SVG Working Group - Activity in 2018
No matches.
GitHub
w3c/svgwg
-
10 issues opened.
-
Support background-color on SVG text w3c/svgwg#622, by @AmeliaBR.
-
Confused about 'writing-mode' with 'direction' w3c/svgwg#618, by @RazrFalcon.
-
Unclear step in Text Layout Algorithm (section 11.5) w3c/svgwg#617, by @faceless2.
-
letter-spacing definition "removes" percentage - not possible w3c/svgwg#611, by @dirkschulze.
-
Remove text-decoration-fill and text-decoration-stroke w3c/svgwg#610, by @dirkschulze.
-
text-overflow definition moved from CSS UI to CSS Overflow w3c/svgwg#609, by @dirkschulze.
-
Mask on mask behavior w3c/svgwg#608, by @RazrFalcon.
-
"Sizing properties" section should mention the "use" element w3c/svgwg#607, by @BigBadaboom.
-
Build warnings w3c/svgwg#602, by @dirkschulze.
-
-
11 issues closed.
-
Remove text-decoration-fill and text-decoration-stroke w3c/svgwg#610.
-
Clarify hit testing behavior of <foreignObject> w3c/svgwg#427.
-
Property index (appendix) needs updating w3c/svgwg#82.
-
Drawing vector-effects mentions SVG 1.2T terms w3c/svgwg#578.
-
Mask on mask behavior w3c/svgwg#608.
-
vector-effect host coordinate space is not "screen" w3c/svgwg#582.
-
Replace <opacity-value> with <alpha-value> w3c/svgwg#403.
-
Support SVG 1.1 baseline value for baseline-shift w3c/svgwg#246.
-
23 issues received 66 new comments.
-
"Sizing properties" section should mention the "use" element w3c/svgwg#607 (9 comments by @AmeliaBR, @BigBadaboom, @css-meeting-bot, @dirkschulze, @karip)
-
Resolved value for the 'width' and 'height' geometry properties w3c/svgwg#349 (5 comments by @css-meeting-bot, @dirkschulze, @fsoder)
-
'image' element not defined to fire 'load' event when load happens w3c/svgwg#361 (4 comments by @BigBadaboom, @css-meeting-bot, @dirkschulze)
-
Remove text-decoration-fill and text-decoration-stroke w3c/svgwg#610 (4 comments by @AmeliaBR, @dirkschulze, @Tavmjong)
-
Unclear step in Text Layout Algorithm (section 11.5) w3c/svgwg#617 (3 comments by @faceless2, @karip)
-
White-space only text nodes. w3c/svgwg#352 (3 comments by @css-meeting-bot, @dirkschulze, @longsonr)
-
SVGElement.getBoundingClientRect(): which bounding box? w3c/svgwg#339 (3 comments by @AmeliaBR, @dirkschulze, @fsoder)
-
letter-spacing definition "removes" percentage - not possible w3c/svgwg#611 (3 comments by @AmeliaBR, @dirkschulze)
-
Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592 (3 comments by @css-meeting-bot, @dirkschulze, @ewilligers)
-
how should display:contents affect SVG conditional processing attributes? w3c/svgwg#579 (2 comments by @css-meeting-bot, @dirkschulze)
-
overflow="auto" should be treated as hidden rather than visible w3c/svgwg#329 (2 comments by @dirkschulze)
-
should textPath elements parented to tspans or other textPaths render? w3c/svgwg#580 (2 comments by @css-meeting-bot, @Tavmjong)
-
Specify which attributes/properties are horizontal vs vertical vs other w3c/svgwg#211 (2 comments by @dirkschulze, @fsoder)
-
Support SVG 1.1 baseline value for baseline-shift w3c/svgwg#246 (2 comments by @AmeliaBR, @dirkschulze)
-
Remove redundant <dl> wrapper for the attribute table + prose block of each element w3c/svgwg#113 (1 comment by @dirkschulze)
-
-
11 pull requests opened.
-
Update current/former editors list w3c/svgwg#621, by @AmeliaBR.
-
<path d> parsing spec needs a special case to not use CSS syntax w3c/svgwg#620, by @SimonSapin.
-
Property Index: explain stroke-dasharray % w3c/svgwg#616, by @ewilligers.
-
[References] Fix broken links w3c/svgwg#614, by @ewilligers.
-
Replace alpha-value with opacity values Fix 403 w3c/svgwg#606, by @dirkschulze.
-
Put miter-clip and arcs values at risk. w3c/svgwg#604, by @dirkschulze.
-
Add CSS properties cx, cy, r, rx, ry, x, y to property index. #82 w3c/svgwg#603, by @dirkschulze.
-
-
11 pull requests merged.
-
Property Index: explain stroke-dasharray % w3c/svgwg#616.
-
[References] Fix broken links w3c/svgwg#614.
-
Replace alpha-value with opacity values Fix 403 w3c/svgwg#606.
-
Put miter-clip and arcs values at risk. w3c/svgwg#604.
-
-
2 pull requests closed.
-
Remove at-risk flag from vector-effect values w3c/svgwg#576.
-
11 pull requests received 29 new comments.
-
Remove properties defined by other CSS modules from prperty index tab… w3c/svgwg#612 (7 comments by @dirkschulze, @ewilligers, @Tavmjong)
-
Use DOMMatrix2DInit as parameters for methods. #326 w3c/svgwg#577 (6 comments by @AmeliaBR, @dirkschulze)
-
<path d> parsing spec needs a special case to not use CSS syntax w3c/svgwg#620 (3 comments by @AmeliaBR, @SimonSapin)
-
Make it more clear what the difference is between URL and <url> w3c/svgwg#565 (2 comments by @svgeesus)
-
Clarify that bounding box of foreignObject is hit-teasting target and… w3c/svgwg#613 (2 comments by @svgeesus)
-
Define which dimension percentage values of CSS properties are relet… w3c/svgwg#615 (1 comment by @dirkschulze)
-
Add CSS properties cx, cy, r, rx, ry, x, y to property index. #82 w3c/svgwg#603 (1 comment by @dirkschulze)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
15 issues opened in the SVG Accessibility Task Force.
-
Consider early re-add of role=text w3c/aria#870, by @kensgists.
-
Clarify definition of listitem and how it is used with group role w3c/aria#868, by @schne324.
-
references to tabindex w3c/aria#867, by @michael-n-cooper.
-
aria-controls in web components w3c/aria#864, by @schrotie.
-
“Todo” notice still in rec document w3c/aria#863, by @yatil.
-
spinbutton required and supported properties w3c/aria#861, by @jnurthen.
-
slider required and supported properties w3c/aria#860, by @jnurthen.
-
separator required and supported properties w3c/aria#859, by @jnurthen.
-
Scrollbar required and supported properties w3c/aria#858, by @jnurthen.
-
-
12 issues closed in the SVG Accessibility Task Force.
-
I have to ask this question: role="logo" w3c/aria#540.
-
aria-controls in web components w3c/aria#864.
-
fix role=directory MSAA mapping w3c/aria#520.
-
Section 1.3 User Agent Support references UAIG 1.0 w3c/aria#489.
-
remove line-height declaration from common.css w3c/aria#445.
-
Biblio.js contains SpecRef dups w3c/aria#391.
-
WAI-ARIA 1.1: Missing Tables in Appendix D w3c/aria#331.
-
WAI-ARIA 1.1: Update Authoring Practices links to 1.1 ? w3c/aria#328.
-
20 issues in the SVG Accessibility Task Force received 35 new comments.
-
Clarify use of aria-label on elements with no role w3c/aria#756 (9 comments by @DavidMacDonald, @jcsteh, @jnurthen, @jongund, @prlbr, @Siemenskun)
-
Consider prohibiting author naming certain roles w3c/aria#833 (4 comments by @aleventhal, @carmacleod, @jcsteh, @pkra)
-
Clarify definition of listitem and how it is used with group role w3c/aria#868 (1 comment by @jnurthen)
-
[ROLE PARITY] Determine if any of these mostly unmapped elements require a specific role w3c/aria#698 (1 comment by @aleventhal)
-
w3c/aria#76 (1 comment by @jnurthen)
-
ARIA 1.1: Label navigation landmarks if more than one per page w3c/aria#355 (1 comment by @jnurthen)
-
WAI-ARIA 1.1: Inconsistent value for aria-expanded for role combobox w3c/aria#339 (1 comment by @jnurthen)
-
-
3 pull requests opened in the SVG Accessibility Task Force.
-
listitem role: clarifies use of role=group within role=list w3c/aria#869, by @schne324.
-
-
1 pull request merged in the SVG Accessibility Task Force.
-
2 pull requests in the SVG Accessibility Task Force received 4 new comments.
-
ARIA: Editorial cleanup needed to "Presentational Roles Conflict Reso… w3c/aria#852 (3 comments by @carmacleod, @jnurthen)
-
switch role: removes default value of aria-checked from role definition w3c/aria#865 (1 comment by @schne324)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
10 issues opened in the SVG Accessibility Task Force.
-
No ARIA property for "default" or "submit" button w3c/aria#842, by @aleventhal.
-
Definition description and aria-labelledby w3c/aria#836, by @jnurthen.
-
Duplicate example in aria-hidden attribute section w3c/aria#835, by @carmacleod.
-
7 issues closed in the SVG Accessibility Task Force.
-
article role/HTML5 element semantics w3c/aria#275.
-
Duplicate example in aria-hidden attribute section w3c/aria#835.
-
Agendas: TPAC 2018 w3c/aria#806.
-
Presentation role section doesn't know about table role w3c/aria#819.
-
18 issues in the SVG Accessibility Task Force received 56 new comments.
-
Annotations w3c/aria#749 (15 comments by @aleventhal, @azaroth42, @BigBlueHat, @joanmarie, @TzviyaSiegman)
-
Consider prohibiting author naming certain roles w3c/aria#833 (6 comments by @carmacleod, @jnurthen)
-
aria-relevant: find real-world use cases, consider deprecating it w3c/aria#712 (5 comments by @aleventhal, @JamesCatt, @jnurthen)
-
No ARIA property for "default" or "submit" button w3c/aria#842 (5 comments by @aleventhal, @asurkov, @jnurthen, @stes-acc)
-
Remove the string reflection properties that will be replaced by incompatible element reflection properties w3c/aria#834 (5 comments by @cookiecrook, @jnurthen)
-
Do we need a notifications API in ARIA w3c/aria#832 (3 comments by @aleventhal, @schne324, @slauriat)
-
ARIA: Editorial cleanup needed to "Presentational Roles Conflict Resolution" section w3c/aria#646 (2 comments by @carmacleod)
-
aria-sort recommendation to have it only on ONE header w3c/aria#582 (2 comments by @jnurthen, @tmorehouse)
-
w3c/aria#76 (1 comment by @jnurthen)
-
Editorial: Merge redundant points in Handling Author Errors section w3c/aria#845 (1 comment by @carmacleod)
-
Editorial: Change "Default value(s)" in "Handling Author Errors" into more corrective phrase w3c/aria#843 (1 comment by @carmacleod)
-
Tree Inclusion focus/activedescendant requirements need clarification w3c/aria#841 (1 comment by @carmacleod)
-
ARIA 1.1: Remove children-presentational true from math role w3c/aria#425 (1 comment by @cookiecrook)
-
method to determine how blocks of text are separated (aria-text separation (property)) w3c/aria#699 (1 comment by @mcking65)
-
-
9 pull requests opened in the SVG Accessibility Task Force.
-
Revert last commit - 310461b (#835) due to bogus commit message w3c/aria#847, by @jnurthen.
-
Editorial: Change Default Value to Fallback Value w3c/aria#844, by @jnurthen.
-
Move focus-change-request content from Core-AAM to ARIA w3c/aria#840, by @joanmarie.
-
Duplicate example in aria-hidden attribute section #835 w3c/aria#839, by @carmacleod.
-
7 pull requests merged in the SVG Accessibility Task Force.
-
Move focus-change-request content from Core-AAM to ARIA w3c/aria#840.
-
Duplicate example in aria-hidden attribute section #835 w3c/aria#839.
-
Editorial: Change Default Value to Fallback Value w3c/aria#844.
-
1 pull request closed in the SVG Accessibility Task Force.
-
5 pull requests in the SVG Accessibility Task Force received 10 new comments.
-
Move focus-change-request content from Core-AAM to ARIA w3c/aria#840 (4 comments by @jnurthen, @joanmarie)
-
Editorial: Change Default Value to Fallback Value w3c/aria#844 (3 comments by @jnurthen, @joanmarie)
-
ARIA: Editorial cleanup needed to "Presentational Roles Conflict Reso… w3c/aria#852 (1 comment by @jnurthen)
-
Add content related to role processing and error handling by user agents w3c/aria#851 (1 comment by @jnurthen)
-
Fixes #837 - Remove redundant paragraph from Presentational Roles Con… w3c/aria#846 (1 comment by @carmacleod)
-
TR publications
-
1 document published.
-
Filter Effects Module Level 1 published as a Working Draft. History of Filter Effects Module Level 1
-
Participants
-
1 organization joined.
-
Alibaba Group joined.
-
GitHub
w3c/svgwg
-
15 issues opened.
-
Add non-attached elements to non-rendered elements w3c/svgwg#599, by @dirkschulze.
-
Place of SVG presentation attributes in the CSS cascade w3c/svgwg#596, by @SelenIT.
-
Possible inconsistency with set element and href attribute w3c/svgwg#595, by @waruyama.
-
Browsers do not accept stroke-linejoin 'miter-clip' or 'arcs' w3c/svgwg#592, by @ewilligers.
-
Mark 4 text properties at risk w3c/svgwg#591, by @ewilligers.
-
Defer text content area w3c/svgwg#589, by @dirkschulze.
-
'stop-color' property resolving with 'inherit' value w3c/svgwg#588, by @RazrFalcon.
-
The filter region clipping w3c/svgwg#587, by @RazrFalcon.
-
vector-effect host coordinate space is not "screen" w3c/svgwg#582, by @dirkschulze.
-
pointer-events: remove requirement to scan pixels on images w3c/svgwg#581, by @dirkschulze.
-
should textPath elements parented to tspans or other textPaths render? w3c/svgwg#580, by @heycam.
-
how should display:contents affect SVG conditional processing attributes? w3c/svgwg#579, by @heycam.
-
Drawing vector-effects mentions SVG 1.2T terms w3c/svgwg#578, by @dirkschulze.
-
pointer-events auto w3c/svgwg#574, by @ewilligers.
-
Defer pointer-events bounding-box? w3c/svgwg#573, by @ewilligers.
-
-
25 issues closed.
-
Rotating text w3c/svgwg#260.
-
UTF-16 code points for addressable characters w3c/svgwg#259.
-
Keep xlink:href in examples linked to in spec. w3c/svgwg#105.
-
definition of character w3c/svgwg#263.
-
'typographic character' should mention grapheme clusters w3c/svgwg#262.
-
Reference W3C Web Animations w3c/svgwg#22.
-
Merge CR changes into master & update to track changes vs CR w3c/svgwg#275.
-
Place of SVG presentation attributes in the CSS cascade w3c/svgwg#596.
-
stroke-width initial value must include units w3c/svgwg#529.
-
SVGGeometry.prototype.isPointInStroke vs. vector-effects w3c/svgwg#559.
-
Add non-attached elements to non-rendered elements w3c/svgwg#599.
-
Possible inconsistency with set element and href attribute w3c/svgwg#595.
-
Defer z-index due to lack of implementations w3c/svgwg#553.
-
'stop-color' property resolving with 'inherit' value w3c/svgwg#588.
-
The filter region clipping w3c/svgwg#587.
-
stroke-miterlimit: invalid value behavior? w3c/svgwg#545.
-
pointer-events: remove requirement to scan pixels on images w3c/svgwg#581.
-
pointer-events auto w3c/svgwg#574.
-
typo: Elmenent w3c/svgwg#569.
-
1 issue reopened.
-
Replace <opacity-value> with <alpha-value> w3c/svgwg#403, by @ewilligers.
-
-
50 issues received 140 new comments.
-
Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. w3c/svgwg#537 (22 comments by @AmeliaBR, @BigBadaboom, @dirkschulze, @fantasai, @litherum, @r12a, @Tavmjong)
-
should textPath elements parented to tspans or other textPaths render? w3c/svgwg#580 (9 comments by @AmeliaBR, @dirkschulze, @fsoder, @heycam, @tabatkins)
-
isPointInFill/isPointInStroke and display: none and other specifics w3c/svgwg#456 (9 comments by @css-meeting-bot, @dirkschulze, @fsoder, @longsonr)
-
'stop-color' property resolving with 'inherit' value w3c/svgwg#588 (6 comments by @dirkschulze, @fsoder, @RazrFalcon, @Tavmjong)
-
Defer pointer-events bounding-box? w3c/svgwg#573 (5 comments by @dirkschulze, @ewilligers, @longsonr)
-
Replace <opacity-value> with <alpha-value> w3c/svgwg#403 (5 comments by @dirkschulze, @ewilligers, @fsoder, @svgeesus)
-
vector-effect host coordinate space is not "screen" w3c/svgwg#582 (5 comments by @css-meeting-bot, @dirkschulze)
-
Remove un-implemented `pointer-events` "painted" rules for images w3c/svgwg#322 (5 comments by @css-meeting-bot, @dirkschulze, @fsoder)
-
Rewrite all element descriptions to use normative language w3c/svgwg#111 (4 comments by @AmeliaBR, @dirkschulze)
-
Defer z-index due to lack of implementations w3c/svgwg#553 (3 comments by @dirkschulze, @ewilligers)
-
pointer-events: remove requirement to scan pixels on images w3c/svgwg#581 (3 comments by @BigBadaboom, @dirkschulze)
-
Marker element percentages are missing reference values w3c/svgwg#64 (2 comments by @AmeliaBR, @dirkschulze)
-
patternTransform browser implementations do not match spec w3c/svgwg#293 (2 comments by @AmeliaBR, @dirkschulze)
-
Add stub pages to SVG 2 for chapters that have been moved to separate specs w3c/svgwg#195 (2 comments by @AmeliaBR, @dirkschulze)
-
Review property value definitions to ensure unitless lengths are correctly included w3c/svgwg#534 (2 comments by @dirkschulze, @ewilligers)
-
Place of SVG presentation attributes in the CSS cascade w3c/svgwg#596 (2 comments by @AmeliaBR, @SelenIT)
-
How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties w3c/svgwg#323 (2 comments by @css-meeting-bot, @dirkschulze)
-
Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts w3c/svgwg#249 (1 comment by @dirkschulze)
-
Check whether behaviour of new CSS3 units needs clarification in SVG context w3c/svgwg#207 (1 comment by @dirkschulze)
-
Figure out where the list of aria-properties comes from, & sort them in logical/alphabetical order w3c/svgwg#117 (1 comment by @dirkschulze)
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335 (1 comment by @dirkschulze)
-
getScreenCTM (and friends?) results for elements that are not in the rendering tree? w3c/svgwg#307 (1 comment by @dirkschulze)
-
Update property definitions to use new CSS approach to "animatable" w3c/svgwg#555 (1 comment by @dirkschulze)
-
'image' element not defined to fire 'load' event when load happens w3c/svgwg#361 (1 comment by @svgeesus)
-
Develop a new standard for describing "layers" in SVG authoring tools w3c/svgwg#68 (1 comment by @dirkschulze)
-
SVGTransform's setMatrix method should take a DOMMatrix2DInit w3c/svgwg#326 (1 comment by @css-meeting-bot)
-
how should display:contents affect SVG conditional processing attributes? w3c/svgwg#579 (1 comment by @dirkschulze)
-
Add decode() and decoding attribute to SVGImageElement w3c/svgwg#373 (1 comment by @css-meeting-bot)
-
Define how new sizing keywords are resolved for SVG width and height geometry properties w3c/svgwg#469 (1 comment by @css-meeting-bot)
-
SVGGeometry.prototype.isPointInStroke vs. vector-effects w3c/svgwg#559 (1 comment by @css-meeting-bot)
-
Proposal for addition of new commands in the Path Data language w3c/svgwg#572 (1 comment by @ratishphilip)
-
-
14 pull requests opened.
-
stop-opacity computed value is clamped w3c/svgwg#601, by @ewilligers.
-
Add detached elements to non-rendered elements. #599 w3c/svgwg#600, by @dirkschulze.
-
Fixes #596 w3c/svgwg#598, by @SelenIT.
-
Fix href in animation w3c/svgwg#597, by @birtles.
-
Painting: numeric stroke-width, stroke-dashoffset w3c/svgwg#593, by @ewilligers.
-
inline-size has initial value auto w3c/svgwg#590, by @ewilligers.
-
isPointInStroke must take vector-effect property into account. #559 w3c/svgwg#583, by @dirkschulze.
-
Use DOMMatrix2DInit as parameters for methods. #326 w3c/svgwg#577, by @dirkschulze.
-
Remove at-risk flag from vector-effect values w3c/svgwg#576, by @dirkschulze.
-
[interactivity] pointer-events auto w3c/svgwg#575, by @ewilligers.
-
-
10 pull requests merged.
-
Fixes #596 w3c/svgwg#598.
-
stop-opacity computed value is clamped w3c/svgwg#601.
-
Add detached elements to non-rendered elements. #599 w3c/svgwg#600.
-
Fix href in animation w3c/svgwg#597.
-
inline-size has initial value auto w3c/svgwg#590.
-
[interactivity] pointer-events auto w3c/svgwg#575.
-
-
1 pull request closed.
-
Painting: numeric stroke-width, stroke-dashoffset w3c/svgwg#593.
-
-
11 pull requests received 30 new comments.
-
Unify CSS properties, use new animation type attributes, allow number… w3c/svgwg#586 (7 comments by @birtles, @dirkschulze)
-
'd' presentation attribute: use path() function w3c/svgwg#374 (5 comments by @css-meeting-bot, @dirkschulze, @ewilligers, @Tavmjong)
-
Adapt host coordinate space def of vector-effect to implemented behav… w3c/svgwg#585 (2 comments by @dirkschulze, @svgeesus)
-
Clarify possible UA behavior on getTotalLength, getPointAtLength, get… w3c/svgwg#594 (2 comments by @dirkschulze, @ewilligers)
-
CSS pointer-events on (raster) images does not require scanning pixels w3c/svgwg#584 (2 comments by @dirkschulze, @svgeesus)
-
Remove iframe, video, audio, canvas and unknown elements due to lack … w3c/svgwg#571 (1 comment by @svgeesus)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
8 issues opened in the SVG Accessibility Task Force.
-
Consider prohibiting author naming certain roles w3c/aria#833, by @joanmarie.
-
Do we need a notifications API in ARIA w3c/aria#832, by @jnurthen.
-
Investigate if we need to add URL to validator w3c/aria#831, by @jnurthen.
-
Prep for October ARIA 1.2 (aka "1.2.2") Working Draft w3c/aria#827, by @joanmarie.
-
Presentation role section doesn't know about table role w3c/aria#819, by @carmacleod.
-
-
3 issues closed in the SVG Accessibility Task Force.
-
New Accessibility Tree section needs intro w3c/aria#811.
-
9 issues in the SVG Accessibility Task Force received 24 new comments.
-
method to determine how blocks of text are separated (aria-text separation (property)) w3c/aria#699 (13 comments by @carmacleod, @cookiecrook, @joanmarie, @mcking65, @melanierichards)
-
Presentation role section doesn't know about table role w3c/aria#819 (2 comments by @carmacleod, @joanmarie)
-
role="timer" has implicit aria-live=off, consider options for interval announcements w3c/aria#821 (2 comments by @DavidMacDonald, @jnurthen)
-
A case perform about focus differently between Chrome + VoiceOver and Safari + VoiceOver w3c/aria#825 (1 comment by @jnurthen)
-
Checkbox has aria-checked required, but there is a default value for aria-checked w3c/aria#826 (1 comment by @carmacleod)
-
-
7 pull requests opened in the SVG Accessibility Task Force.
-
Move ID Errors section from core aam w3c/aria#830, by @jnurthen.
-
Move Special Document Handling section from core-aam to aria w3c/aria#829, by @jnurthen.
-
[WIP] Merge remaining changes from #813 into stable w3c/aria#828, by @joanmarie.
-
Presentation role section doesn't know about table role #819 w3c/aria#824, by @carmacleod.
-
Make it clearer that timeline may change w3c/aria#823, by @plehegar.
-
Fix typo in aria-live description w3c/aria#822, by @nicolas17.
-
Additional considerations regarding mapping implementation w3c/aria#820, by @plehegar.
-
-
8 pull requests merged in the SVG Accessibility Task Force.
-
Make it clearer that timeline may change w3c/aria#823.
-
Move ID Errors section from core aam w3c/aria#830.
-
Fix typo in aria-live description w3c/aria#822.
-
4 pull requests in the SVG Accessibility Task Force received 13 new comments.
-
[WIP] Merge keyboard navigation content from Core AAM into Managing Focus w3c/aria#801 (10 comments by @jnurthen, @joanmarie)
-
Role spinbutton: allow empty values, no min, no max, and structure with sibling steppers w3c/aria#813 (1 comment by @joanmarie)
-
TR publications
-
2 documents published.
-
Scalable Vector Graphics (SVG) 2 published as a Candidate Recommendation Snapshot. History of Scalable Vector Graphics (SVG) 2
-
Web Animations published as a Working Draft. History of Web Animations
-
GitHub
w3c/svgwg
-
11 issues opened.
-
Proposal for addition of new commands in the Path Data language w3c/svgwg#572, by @ratishphilip.
-
typo: Elmenent w3c/svgwg#569, by @1jj.
-
Defer HTML media elements in SVG 2.0 w3c/svgwg#563, by @dirkschulze.
-
Syntactic forms: URL and <url> section is unclear or even wrong w3c/svgwg#562, by @dirkschulze.
-
Add an event for zoom level changes w3c/svgwg#561, by @Zhang-Junzhi.
-
<circle> with r=0 - disabled or not? w3c/svgwg#560, by @fsoder.
-
SVGGeometry.prototype.isPointInStroke vs. vector-effects w3c/svgwg#559, by @fsoder.
-
Editorial: isPointInStroke references HTML w3c/svgwg#557, by @fsoder.
-
Update property definitions to use new CSS approach to "animatable" w3c/svgwg#555, by @AmeliaBR.
-
Defer z-index due to lack of implementations w3c/svgwg#553, by @EdorianDark.
-
-
6 issues closed.
-
<circle> with r=0 - disabled or not? w3c/svgwg#560.
-
Editorial: isPointInStroke references HTML w3c/svgwg#557.
-
Move Web Animations out of normative references w3c/svgwg#365.
-
-
1 issue reopened.
-
earls w3c/svgwg#554, by @lodgerwright.
-
-
28 issues received 83 new comments.
-
Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. w3c/svgwg#537 (15 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @fantasai, @kojiishi, @litherum, @r12a)
-
SVGGeometry.prototype.isPointInStroke vs. vector-effects w3c/svgwg#559 (11 comments by @AmeliaBR, @dirkschulze, @fsoder)
-
Need to better define what rules apply to an element in an <svg:use> subtree. w3c/svgwg#504 (7 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @emilio)
-
'color-interpolation' isn't used for alpha compositing w3c/svgwg#366 (7 comments by @AmeliaBR, @BigBadaboom, @sobotka, @svgeesus, @thomasmansencal)
-
<circle> with r=0 - disabled or not? w3c/svgwg#560 (5 comments by @AmeliaBR, @dirkschulze, @EdorianDark, @tabatkins)
-
Add use and symbol elements to the Geometry Properties section w3c/svgwg#525 (3 comments by @css-meeting-bot, @dirkschulze)
-
Add decode() and decoding attribute to SVGImageElement w3c/svgwg#373 (3 comments by @AmeliaBR, @dirkschulze)
-
Define how new sizing keywords are resolved for SVG width and height geometry properties w3c/svgwg#469 (3 comments by @AmeliaBR, @dirkschulze)
-
Editorial(ish): Incorrect method reference in algorithm for checkIntersection/checkEnclosure w3c/svgwg#558 (2 comments by @dirkschulze, @fsoder)
-
Suggest dropping requirement for text-align-all and text-space-collapse w3c/svgwg#486 (2 comments by @ewilligers, @svgeesus)
-
The interpolation of large_arc_flag/sweep_flag of Elliptical Arc in SVG Path w3c/svgwg#543 (2 comments by @svgeesus, @tabatkins)
-
What is the unit type after setting an SVGAngle or SVGLength's value w3c/svgwg#478 (2 comments by @AmeliaBR, @css-meeting-bot)
-
Proposal for addition of new commands in the Path Data language w3c/svgwg#572 (1 comment by @litherum)
-
Syntactic forms: URL and <url> section is unclear or even wrong w3c/svgwg#562 (1 comment by @AmeliaBR)
-
Update property definitions to use new CSS approach to "animatable" w3c/svgwg#555 (1 comment by @svgeesus)
-
We should define the behavior of ‘use’ in terms of Web Components w3c/svgwg#99 (1 comment by @AmeliaBR)
-
-
8 pull requests opened.
-
Fix type on 'Element' in changes section w3c/svgwg#570, by @dirkschulze.
-
<circle> with r=0 has rendering disabled w3c/svgwg#568, by @ewilligers.
-
Fix accidental linking issues to HTML Canvas. #557 w3c/svgwg#567, by @dirkschulze.
-
Make it more clear what the difference is between URL and <url> w3c/svgwg#565, by @dirkschulze.
-
Fix Web IDL typo: PutsForwards -> PutForwards w3c/svgwg#564, by @foolip.
-
Change definition of "addressable character" for text positioning att… w3c/svgwg#556, by @Tavmjong.
-
5 pull requests merged.
-
Fix type on 'Element' in changes section w3c/svgwg#570.
-
<circle> with r=0 has rendering disabled w3c/svgwg#568.
-
Fix accidental linking issues to HTML Canvas. #557 w3c/svgwg#567.
-
Fix Web IDL typo: PutsForwards -> PutForwards w3c/svgwg#564.
-
519 kill local coords w3c/svgwg#552.
-
-
1 pull request closed.
-
8 pull requests received 32 new comments.
-
Remove iframe, video, audio, canvas and unknown elements due to lack … w3c/svgwg#571 (13 comments by @AmeliaBR, @dirkschulze)
-
Fix accidental linking issues to HTML Canvas. #557 w3c/svgwg#567 (8 comments by @AmeliaBR, @dirkschulze)
-
'd' presentation attribute: use path() function w3c/svgwg#374 (3 comments by @AmeliaBR, @dirkschulze)
-
Make it more clear what the difference is between URL and <url> w3c/svgwg#565 (2 comments by @AmeliaBR)
-
Change definition of "addressable character" for text positioning att… w3c/svgwg#556 (2 comments by @AmeliaBR, @BigBadaboom)
-
Re-add text that would request to disable rendering an element if the… w3c/svgwg#566 (1 comment by @AmeliaBR)
-
GitHub
w3c/svgwg
-
6 issues opened.
-
Should setting an enum IDL to an invalid value throw an error? w3c/svgwg#547, by @AmeliaBR.
-
Extend SVGAnimatedString with putForwards/stringifier WebIDL behaviors w3c/svgwg#546, by @AmeliaBR.
-
stroke-miterlimit: invalid value behavior? w3c/svgwg#545, by @AmeliaBR.
-
Set up pre-merge test build checks for Pull Requests w3c/svgwg#541, by @AmeliaBR.
-
Incorrect Bounding Box Demonstration Result in Specification w3c/svgwg#538, by @tonyhallett.
-
-
10 issues closed.
-
Update/move the normative-but-outdated SVG DOM appendix w3c/svgwg#520.
-
:host(use) > symbol in a UA sheet does nothing. w3c/svgwg#502.
-
Add <use> to the graphics elements category w3c/svgwg#229.
-
ICC support in Conforming High-Quality SVG viewer w3c/svgwg#532.
-
Emojis and SVG <text> inconsistency w3c/svgwg#381.
-
SVG 1.1 Errata: How to Proceed? w3c/svgwg#390.
-
References needs a thorough overhaul w3c/svgwg#514.
-
Incorrect Bounding Box Demonstration Result in Specification w3c/svgwg#538.
-
-
24 issues received 111 new comments.
-
Serialization format for path strings w3c/svgwg#321 (32 comments by @AmeliaBR, @birtles, @BorisChiou, @css-meeting-bot, @emilio, @ewilligers, @svgeesus, @tabatkins, @tigt)
-
The interpolation of large_arc_flag/sweep_flag of Elliptical Arc in SVG Path w3c/svgwg#543 (16 comments by @AmeliaBR, @birtles, @BorisChiou, @css-meeting-bot, @ewilligers, @svgeesus, @tabatkins)
-
Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. w3c/svgwg#537 (12 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @fsoder, @svgeesus, @Tavmjong)
-
:host(use) > symbol in a UA sheet does nothing. w3c/svgwg#502 (8 comments by @AmeliaBR, @css-meeting-bot, @svgeesus, @tabatkins)
-
Update/move the normative-but-outdated SVG DOM appendix w3c/svgwg#520 (8 comments by @AmeliaBR, @css-meeting-bot, @svgeesus)
-
stroke-miterlimit: invalid value behavior? w3c/svgwg#545 (6 comments by @AmeliaBR, @css-meeting-bot, @fsoder)
-
Should setting an enum IDL to an invalid value throw an error? w3c/svgwg#547 (3 comments by @AmeliaBR, @birtles, @css-meeting-bot)
-
Identify SVG1 elements that are obsolete in SVG2 w3c/svgwg#448 (3 comments by @css-meeting-bot, @svgeesus)
-
Use the term "user coordinate system" instead of "local coordinate system" w3c/svgwg#519 (2 comments by @css-meeting-bot, @svgeesus)
-
Set up pre-merge test build checks for Pull Requests w3c/svgwg#541 (2 comments by @AmeliaBR, @svgeesus)
-
Review property value definitions to ensure unitless lengths are correctly included w3c/svgwg#534 (2 comments by @svgeesus)
-
Incorrect Bounding Box Demonstration Result in Specification w3c/svgwg#538 (2 comments by @BigBadaboom, @tonyhallett)
-
Consider adding a switch to control how Addresssable Characters are treated w3c/svgwg#280 (2 comments by @AmeliaBR)
-
What is the unit type after setting an SVGAngle or SVGLength's value w3c/svgwg#478 (1 comment by @AmeliaBR)
-
Extend SVGAnimatedString with putForwards/stringifier WebIDL behaviors w3c/svgwg#546 (1 comment by @AmeliaBR)
-
Make SVGAnimatedX data types extend DOMX data types wherever possible w3c/svgwg#175 (1 comment by @AmeliaBR)
-
-
9 pull requests opened.
-
519 kill local coords w3c/svgwg#552, by @svgeesus.
-
Allow any non-negative number for stroke-miterlimit w3c/svgwg#551, by @AmeliaBR.
-
Tidying up, post-"No normative appendices" w3c/svgwg#550, by @AmeliaBR.
-
Fix #532 with informative refs to ICC & ICC support in css-color-4 w3c/svgwg#549, by @svgeesus.
-
No normative appendices! w3c/svgwg#548, by @AmeliaBR.
-
Change from HTML 5.1 to HTML LS, #514 w3c/svgwg#544, by @svgeesus.
-
Add stub files for removed chapters/appendices w3c/svgwg#542, by @AmeliaBR.
-
Reintroduce segment-completing closepath as a theoretical concept w3c/svgwg#540, by @AmeliaBR.
-
Revert & replace changes from PR #495 w3c/svgwg#539, by @AmeliaBR.
-
-
9 pull requests merged.
-
Tidying up, post-"No normative appendices" w3c/svgwg#550.
-
Allow any non-negative number for stroke-miterlimit w3c/svgwg#551.
-
No normative appendices! w3c/svgwg#548.
-
Change from HTML 5.1 to HTML LS, #514 w3c/svgwg#544.
-
Clarify character related definitions. #263, #262, #259. w3c/svgwg#522.
-
Add stub files for removed chapters/appendices w3c/svgwg#542.
-
Revert & replace changes from PR #495 w3c/svgwg#539.
-
-
9 pull requests received 53 new comments.
-
Fix #532 with informative refs to ICC & ICC support in css-color-4 w3c/svgwg#549 (3 comments by @AmeliaBR, @svgeesus)
-
Reintroduce segment-completing closepath as a theoretical concept w3c/svgwg#540 (1 comment by @ewilligers)
SVG Accessibility Task Force
GitHub
w3c/aria
-
4 issues opened in the SVG Accessibility Task Force.
-
Columnheader roles do not work with the abbr attribute w3c/aria#816, by @7mary4.
-
I think we need a definition of "User Interface Element" w3c/aria#815, by @DavidMacDonald.
-
8 issues in the SVG Accessibility Task Force received 35 new comments.
-
Agendas: TPAC 2018 w3c/aria#806 (16 comments by @aleventhal, @bakkenb, @BigBlueHat, @carmacleod, @DavidMacDonald, @jnurthen, @joanmarie, @mcking65, @stes-acc, @TzviyaSiegman, @yatil)
-
I think we need a definition of "User Interface Element" w3c/aria#815 (5 comments by @carmacleod, @devarshipant, @jnurthen, @stes-acc)
-
method to determine how blocks of text are separated (aria-text separation (property)) w3c/aria#699 (3 comments by @carmacleod, @melanierichards)
-
Update 'combobox' spec as per html spec/html-aam mapping for <select> element w3c/aria#817 (3 comments by @accdc, @carmacleod, @stes-acc)
-
Roles, states, and properties to support an accordion pattern w3c/aria#530 (2 comments by @carmacleod, @stes-acc)
-
Need an aria-interactive attribute to indicate a control has its own keyboard handlers w3c/aria#746 (1 comment by @stes-acc)
-
-
1 pull request opened in the SVG Accessibility Task Force.
-
New Accessibility Tree section needs intro #811 w3c/aria#814, by @carmacleod.
-
-
1 pull request merged in the SVG Accessibility Task Force.
-
New Accessibility Tree section needs intro #811 w3c/aria#814.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
5 pull requests in the SVG Accessibility Task Force received 22 new comments.
-
initial draft for role="generic" issue #699 w3c/aria#805 (15 comments by @carmacleod, @mcking65, @melanierichards)
-
Option role: Change aria-selected from required to supported and remove default value w3c/aria#799 (3 comments by @aleventhal, @asurkov, @melanierichards)
-
Core-AAM: Correct issues in aria-readonly mapping for MSAA/IA2: w3c/aria#619 (1 comment by @joanmarie)
-
[WIP] Merge keyboard navigation content from Core AAM into Managing Focus w3c/aria#801 (1 comment by @carmacleod)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
10 issues opened in the SVG Accessibility Task Force.
-
Allowed structures for spinbutton widgets is ambiguous w3c/aria#812, by @mcking65.
-
New Accessibility Tree section needs intro w3c/aria#811, by @carmacleod.
-
Required Context Role for option has bulleted list (inconsistent) w3c/aria#807, by @carmacleod.
-
Agendas: TPAC 2018 w3c/aria#806, by @jnurthen.
-
aria-role should be reserved for 'purpose' not 'form-factor' w3c/aria#804, by @Meteor0id.
-
Duplicate content in ARIA Technique 19 w3c/aria#800, by @plannero.
-
-
2 issues closed in the SVG Accessibility Task Force.
-
Duplicate content in ARIA Technique 19 w3c/aria#800.
-
18 issues in the SVG Accessibility Task Force received 54 new comments.
-
method to determine how blocks of text are separated (aria-text separation (property)) w3c/aria#699 (17 comments by @AmeliaBR, @carmacleod, @cookiecrook, @jnurthen, @mcking65)
-
Option role has confusing/contradictory/circular context roles specified w3c/aria#809 (6 comments by @carmacleod, @jnurthen)
-
Required properties and default values w3c/aria#787 (4 comments by @annethyme, @carmacleod, @jnurthen)
-
ARIA 1.1: aria-expanded is not supported on menuitem roles w3c/aria#454 (3 comments by @jnurthen, @jspurlin)
-
aria-role should be reserved for 'purpose' not 'form-factor' w3c/aria#804 (3 comments by @carmacleod, @jnurthen, @mcking65)
-
Need an aria-interactive attribute to indicate a control has its own keyboard handlers w3c/aria#746 (3 comments by @carmacleod, @devarshipant)
-
aria-controls should only point to visible elements w3c/aria#531 (3 comments by @LJWatson, @mcking65, @StommePoes)
-
aria-required vs required: spec mismatch between ARIA 1.1 and HTML 5.1 w3c/aria#433 (1 comment by @carmacleod)
-
aria-errormessage spec suggests aria-invalid state affects rendering of error element w3c/aria#796 (1 comment by @carmacleod)
-
Make aria-valuenow supported instead of required for spinbutton role w3c/aria#797 (1 comment by @jnurthen)
-
Slider: Specify a decimal value for valuenow, valuemin, valuemax w3c/aria#706 (1 comment by @mcking65)
-
-
8 pull requests opened in the SVG Accessibility Task Force.
-
Editorial nits in role-description for group w3c/aria#810, by @carmacleod.
-
initial draft for role="generic" issue #699 w3c/aria#805, by @carmacleod.
-
Add code fences to README w3c/aria#803, by @nschonni.
-
Typos in README w3c/aria#802, by @nschonni.
-
7 pull requests merged in the SVG Accessibility Task Force.
-
Editorial nits in role-description for group w3c/aria#810.
-
Add code fences to README w3c/aria#803.
-
Typos in README w3c/aria#802.
-
1 pull request closed in the SVG Accessibility Task Force.
-
Add a "Supporting Keyboard Navigation" section w3c/aria#793.
-
-
9 pull requests in the SVG Accessibility Task Force received 21 new comments.
-
[WIP] Merge keyboard navigation content from Core AAM into Managing Focus w3c/aria#801 (9 comments by @mcking65)
-
Add an "Accessibility Tree" section describing inclusion and exclusion rules w3c/aria#792 (4 comments by @carmacleod, @charmarkk, @joanmarie, @melanierichards)
-
Rowheader Role: Correct normative context requirement and make editorial improvements w3c/aria#790 (1 comment by @carmacleod)
-
Row Role: allow aria-posinset and aria-setsize for issue 558 w3c/aria#789 (1 comment by @carmacleod)
-
TR publications
-
1 document published.
-
Scalable Vector Graphics (SVG) 2 published as a Candidate Recommendation Snapshot. History of Scalable Vector Graphics (SVG) 2
-
Participants
-
1 participant left.
-
Liam Quin (W3C) left.
-
-
1 organization left.
-
IBM Corporation left.
-
GitHub
w3c/svgwg
-
13 issues opened.
-
ICC support in Conforming High-Quality SVG viewer w3c/svgwg#532, by @svgeesus.
-
stroke-width initial value must include units w3c/svgwg#529, by @sideshowbarker.
-
Add use and symbol elements to the Geometry Properties section w3c/svgwg#525, by @karip.
-
Update/move the normative-but-outdated SVG DOM appendix w3c/svgwg#520, by @AmeliaBR.
-
text chunk, current text position, and text-anchor w3c/svgwg#518, by @GLRoylance.
-
systemLanguage is not clear about case-insensitive matches w3c/svgwg#517, by @GLRoylance.
-
References needs a thorough overhaul w3c/svgwg#514, by @svgeesus.
-
security and privacy considerations w3c/svgwg#513, by @svgeesus.
-
<foreignObject> and <svg:use> w3c/svgwg#511, by @emilio.
-
12 issues closed.
-
Defer CSS child selectors to SVG 2.1 or a CSS spec w3c/svgwg#507.
-
systemLanguage is not clear about case-insensitive matches w3c/svgwg#517.
-
Add a UA stylesheet rule requiring pointer cursor over links w3c/svgwg#468.
-
Consider if XSL references can be removed w3c/svgwg#227.
-
Wrong description of "visibility" property w3c/svgwg#405.
-
Incorrect syntax for <child-selector> dfn w3c/svgwg#498.
-
Remove left-over references to solid-color and solid-opacity w3c/svgwg#474.
-
-
1 issue reopened.
-
stroke-width initial value must include units w3c/svgwg#529, by @AmeliaBR.
-
-
28 issues received 79 new comments.
-
stroke-width initial value must include units w3c/svgwg#529 (13 comments by @AmeliaBR, @dirkschulze, @ewilligers, @sideshowbarker, @svgeesus)
-
Wrong description of percentage units w3c/svgwg#406 (7 comments by @AmeliaBR, @css-meeting-bot, @ewilligers, @jarek-foksa, @svgeesus)
-
systemLanguage is not clear about case-insensitive matches w3c/svgwg#517 (5 comments by @AmeliaBR, @fsoder, @jarek-foksa, @longsonr)
-
Add support for the `hidden`-attribute w3c/svgwg#508 (4 comments by @AmeliaBR, @fsoder, @simevidas, @tigt)
-
Review property value definitions to ensure unitless lengths are correctly included w3c/svgwg#534 (3 comments by @css-meeting-bot, @ewilligers)
-
Update/move the normative-but-outdated SVG DOM appendix w3c/svgwg#520 (3 comments by @AmeliaBR, @css-meeting-bot, @svgeesus)
-
Target attribute on `a`: consistency with HTML or with existing implementations? w3c/svgwg#526 (3 comments by @dstorey, @ewilligers, @smfr)
-
Need to better define what rules apply to an element in an <svg:use> subtree. w3c/svgwg#504 (2 comments by @emilio)
-
'd' presentation attribute inconsistent with shipped implementation and offset-path w3c/svgwg#320 (2 comments by @css-meeting-bot, @svgeesus)
-
Use the term "user coordinate system" instead of "local coordinate system" w3c/svgwg#519 (2 comments by @jarek-foksa, @svgeesus)
-
Review of L.2.1 changes across the whole document - status w3c/svgwg#392 (2 comments by @liamquin, @svgeesus)
-
C.4.2 out-of-range flag values note is invalid/unsupported, should be dropped w3c/svgwg#324 (2 comments by @AmeliaBR, @svgeesus)
-
Use CSS gradient rules for transitioning semi-transparent stop-colors w3c/svgwg#180 (1 comment by @echuber2)
-
Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. w3c/svgwg#537 (1 comment by @css-meeting-bot)
-
SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString w3c/svgwg#315 (1 comment by @AmeliaBR)
-
Add use and symbol elements to the Geometry Properties section w3c/svgwg#525 (1 comment by @AmeliaBR)
-
The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. w3c/svgwg#297 (1 comment by @svgeesus)
-
Update SVG WG Feedback page on w3.org to point to GitHub issues w3c/svgwg#216 (1 comment by @svgeesus)
-
-
15 pull requests opened.
-
link cursor to UA stylesheet, closes #468 w3c/svgwg#536, by @svgeesus.
-
Refs overhaul issue 514 w3c/svgwg#535, by @svgeesus.
-
Defer child keyword and child CSS function from paint. #507 w3c/svgwg#533, by @dirkschulze.
-
No need for XSL-FO, fixes issue 227 w3c/svgwg#531, by @svgeesus.
-
Change stroke-width initial value to 1px w3c/svgwg#530, by @sideshowbarker.
-
Language tags are case-insensitive. Closes #517 w3c/svgwg#528, by @GLRoylance.
-
Make examples xml valid. w3c/svgwg#527, by @JohnLukeBentley.
-
Build & local dev fixes w3c/svgwg#524, by @AmeliaBR.
-
Make "Example of text auto-wrapped" example valid. w3c/svgwg#523, by @JohnLukeBentley.
-
Clarify character related definitions. #263, #262, #259. w3c/svgwg#522, by @Tavmjong.
-
Clean-up Changes appendix w3c/svgwg#521, by @AmeliaBR.
-
remove dangling mention of SolidColor from chapter title w3c/svgwg#512, by @svgeesus.
-
Consistently say dominant-baseline is inherited w3c/svgwg#510, by @ewilligers.
-
-
20 pull requests merged.
-
Defer child keyword and child CSS function from paint. #507 w3c/svgwg#533.
-
Build & local dev fixes w3c/svgwg#524.
-
Language tags are case-insensitive. Closes #517 w3c/svgwg#528.
-
link cursor to UA stylesheet, closes #468 w3c/svgwg#536.
-
Refs overhaul issue 514 w3c/svgwg#535.
-
Remove support for segment-completing close path w3c/svgwg#398.
-
Consistently say dominant-baseline is inherited w3c/svgwg#510.
-
Marker: update <child-selector> syntax w3c/svgwg#500.
-
Use class="extract" to exclude IDL w3c/svgwg#495.
-
No need for XSL-FO, fixes issue 227 w3c/svgwg#531.
-
Change stroke-width initial value to 1px w3c/svgwg#530.
-
Make examples xml valid. w3c/svgwg#527.
-
Update SVGAElement to match attributes on HTMLAnchorElement w3c/svgwg#409.
-
pathLength does not affect percentage calculations w3c/svgwg#485.
-
Fixes #405 update description of when visibility applies w3c/svgwg#430.
-
Make "Example of text auto-wrapped" example valid. w3c/svgwg#523.
-
Clean-up Changes appendix w3c/svgwg#521.
-
Issue 324 w3c/svgwg#516.
-
Issue 514 w3c/svgwg#515.
-
remove dangling mention of SolidColor from chapter title w3c/svgwg#512.
-
-
1 pull request closed.
-
Clarify that mesh and hatch have been deferred w3c/svgwg#481.
-
-
13 pull requests received 29 new comments.
-
Language tags are case-insensitive. Closes #517 w3c/svgwg#528 (5 comments by @AmeliaBR, @ewilligers, @GLRoylance)
-
Update SVGAElement to match attributes on HTMLAnchorElement w3c/svgwg#409 (3 comments by @AmeliaBR, @css-meeting-bot)
-
Make "Example of text auto-wrapped" example valid. w3c/svgwg#523 (3 comments by @JohnLukeBentley, @Tavmjong)
-
'd' presentation attribute: use path() function w3c/svgwg#374 (2 comments by @dirkschulze, @ewilligers)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
5 issues opened in the SVG Accessibility Task Force.
-
Questions regarding aria-haspopup w3c/aria#795, by @kristofferlium.
-
Questions regarding dialog w3c/aria#794, by @kristofferlium.
-
Account information w3c/aria#791, by @sayhurtz33.
-
Required properties and default values w3c/aria#787, by @WilcoFiers.
-
-
4 issues closed in the SVG Accessibility Task Force.
-
Account information w3c/aria#791.
-
12 issues in the SVG Accessibility Task Force received 28 new comments.
-
Propose new attribute for SSML to provide pronunciation or presentational hinting to AT w3c/aria#659 (4 comments by @alia11y, @joanmarie, @michael-n-cooper)
-
Scrollbar aria-orientation required property? w3c/aria#780 (4 comments by @accdc, @joanmarie, @mcking65)
-
role="row" needs to support aria-setsize, aria-posinset w3c/aria#558 (4 comments by @jnurthen, @mcking65, @SiTaggart)
-
Adding roles, states, and properties to support math w3c/aria#660 (2 comments by @asurkov, @joanmarie)
-
Consider moving normative, NON-mapping content from Core AAM to ARIA w3c/aria#779 (2 comments by @joanmarie)
-
Clarify whether alt attribute is valid alternative text for role="img" w3c/aria#783 (1 comment by @jnurthen)
-
-
4 pull requests opened in the SVG Accessibility Task Force.
-
Add a "Supporting Keyboard Navigation" section w3c/aria#793, by @joanmarie.
-
Row Role: allow aria-posinset and aria-setsize for issue 558 w3c/aria#789, by @mcking65.
-
-
3 pull requests merged in the SVG Accessibility Task Force.
-
Issue719 allow group in listbox w3c/aria#782.
-
Issue737 menuitem and groups w3c/aria#784.
-
-
3 pull requests in the SVG Accessibility Task Force received 3 new comments.
Participants
-
1 organization left.
-
Yandex left.
-
GitHub
w3c/svgwg
-
20 issues opened.
-
CSS syntax on SVG only attributes w3c/svgwg#509, by @dirkschulze.
-
Add support for the `hidden`-attribute w3c/svgwg#508, by @ZoeBijl.
-
Defer CSS child selectors to SVG 2.1 or a CSS spec w3c/svgwg#507, by @dirkschulze.
-
Link to tests from SVG spec. w3c/svgwg#506, by @AmeliaBR.
-
:host(use) > symbol in a UA sheet does nothing. w3c/svgwg#502, by @emilio.
-
Consider tagging the <dasharray> production rule w3c/svgwg#499, by @tidoust.
-
Incorrect syntax for <child-selector> dfn w3c/svgwg#498, by @tidoust.
-
<script type='module'... w3c/svgwg#496, by @paradisaeidae.
-
Review implementation support - Basic Data Types and Interfaces w3c/svgwg#494, by @AmeliaBR.
-
Review implementation support - Rendering Model w3c/svgwg#492, by @AmeliaBR.
-
Review implementation support - Conformance Criteria w3c/svgwg#491, by @AmeliaBR.
-
Review implementation support - Intro / whole document w3c/svgwg#488, by @AmeliaBR.
-
Review implementation support - SVG 2 Master issue w3c/svgwg#487, by @AmeliaBR.
-
Review implementation support - Basic Shapes chapter w3c/svgwg#484, by @ewilligers.
-
z-index rendering order not supported by any browser w3c/svgwg#483, by @ewilligers.
-
Remove requirement for 'clip' property support w3c/svgwg#479, by @ewilligers.
-
What is the unit type after setting an SVGAngle or SVGLength's value w3c/svgwg#478, by @longsonr.
-
-
8 issues closed.
-
Remove "style attributes" from all element definitions w3c/svgwg#404.
-
Consider tagging the <dasharray> production rule w3c/svgwg#499.
-
Harmonise inline-size with CSS Logical properties w3c/svgwg#436.
-
z-index rendering order not supported by any browser w3c/svgwg#483.
-
Remove requirement for 'clip' property support w3c/svgwg#479.
-
Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit w3c/svgwg#419.
-
-
2 issues reopened.
-
Review implementation support - Embedded Content chapter w3c/svgwg#384, by @AmeliaBR.
-
Review implementation support - Embedded Content chapter w3c/svgwg#384, by @AmeliaBR.
-
-
24 issues received 35 new comments.
-
Suggest dropping requirement for text-align-all and text-space-collapse w3c/svgwg#486 (5 comments by @AmeliaBR, @css-meeting-bot, @ewilligers, @Tavmjong)
-
z-index rendering order not supported by any browser w3c/svgwg#483 (3 comments by @AmeliaBR, @birtles, @jwatt)
-
getPathSegAtLength had consistent implementation behavior for invalid paths w3c/svgwg#313 (2 comments by @css-meeting-bot, @ewilligers)
-
Do we really need not to reflect additional enum values in SVG 2 w3c/svgwg#424 (1 comment by @css-meeting-bot)
-
isPointInFill/isPointInStroke and display: none and other specifics w3c/svgwg#456 (1 comment by @css-meeting-bot)
-
Need to better define what rules apply to an element in an <svg:use> subtree. w3c/svgwg#504 (1 comment by @AmeliaBR)
-
What are local reference URLs resolved against in <svg:use> in a Shadow Tree? w3c/svgwg#505 (1 comment by @AmeliaBR)
-
grammar for "closepath can substitute for final coordinate" is broken w3c/svgwg#325 (1 comment by @css-meeting-bot)
-
'pathLength' interaction with <textPath> with a percentage 'startOffset' w3c/svgwg#383 (1 comment by @css-meeting-bot)
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (1 comment by @css-meeting-bot)
-
-
12 pull requests opened.
-
Remove "style definitions" from all element definitions. Fix wording.… w3c/svgwg#503, by @Tavmjong.
-
Tag production rules with prod class w3c/svgwg#501, by @ewilligers.
-
Marker: update <child-selector> syntax w3c/svgwg#500, by @ewilligers.
-
Update team contacts w3c/svgwg#497, by @tripu.
-
Use class="extract" to exclude IDL w3c/svgwg#495, by @saschanaz.
-
Mark SVGNameList as an example w3c/svgwg#493, by @saschanaz.
-
Do not require text-align-all, text-space-collapse w3c/svgwg#490, by @ewilligers.
-
Defer z-index support from SVG 2 w3c/svgwg#489, by @ewilligers.
-
pathLength does not affect percentage calculations w3c/svgwg#485, by @ewilligers.
-
Inline size: remove 'number' value. w3c/svgwg#482, by @Tavmjong.
-
Clarify that mesh and hatch have been deferred w3c/svgwg#481, by @ewilligers.
-
Remove requirement for clip property support w3c/svgwg#480, by @ewilligers.
-
-
12 pull requests merged.
-
Tag production rules with prod class w3c/svgwg#501.
-
Inline size: remove 'number' value. w3c/svgwg#482.
-
Defer z-index support from SVG 2 w3c/svgwg#489.
-
Do not require text-align-all, text-space-collapse w3c/svgwg#490.
-
Remove left-over references to solid-color and solid-opacity w3c/svgwg#475.
-
Update property index w3c/svgwg#446.
-
Remove requirement for clip property support w3c/svgwg#480.
-
Update team contacts w3c/svgwg#497.
-
Mark SVGNameList as an example w3c/svgwg#493.
-
Textpath pathlength w3c/svgwg#476.
-
remove redundant words w3c/svgwg#477.
-
14 pull requests received 28 new comments.
-
Remove left-over references to solid-color and solid-opacity w3c/svgwg#475 (5 comments by @BigBadaboom, @dirkschulze, @ewilligers)
-
Remove support for segment-completing close path w3c/svgwg#398 (4 comments by @css-meeting-bot, @dirkschulze, @ewilligers)
-
Marker: update <child-selector> syntax w3c/svgwg#500 (3 comments by @css-meeting-bot, @dirkschulze, @ewilligers)
-
Update SVGAElement to match attributes on HTMLAnchorElement w3c/svgwg#409 (3 comments by @AmeliaBR, @dstorey, @ewilligers)
-
w3c/svg-aam
-
1 issue received 8 new comments.
-
TextPath and TSpan need platform-specific mappiings w3c/svg-aam#2 (8 comments by @AmeliaBR, @asurkov, @joanmarie, @melanierichards)
-
GitHub
w3c/svgwg
-
5 issues opened.
-
Remove left-over references to solid-color and solid-opacity w3c/svgwg#474, by @BigBadaboom.
-
Incorrect reference for isolation property w3c/svgwg#472, by @ewilligers.
-
Add a UA stylesheet rule requiring pointer cursor over links w3c/svgwg#468, by @AmeliaBR.
-
Clarify Event attributes section w3c/svgwg#467, by @Ms2ger.
-
-
6 issues closed.
-
Incorrect reference for isolation property w3c/svgwg#472.
-
:hover on overlapping elements w3c/svgwg#371.
-
Where are unitless lengths allowed? What do they mean? w3c/svgwg#379.
-
SVG and CSS display:contents w3c/svgwg#305.
-
Create a wiki page listing deferred SVG 2 features w3c/svgwg#284.
-
-
99 issues received 107 new comments.
-
Excess parenthesis in text layout algorithm? ("Position on path" part) w3c/svgwg#382 (3 comments by @boggydigital, @Tavmjong)
-
Text chapter and definitions.xml still reference shape-outside w3c/svgwg#288 (2 comments by @boggydigital, @Tavmjong)
-
Define how new sizing keywords are resolved for SVG width and height geometry properties w3c/svgwg#469 (2 comments by @boggydigital, @tabatkins)
-
Add a UA stylesheet rule requiring pointer cursor over links w3c/svgwg#468 (2 comments by @boggydigital, @svgeesus)
-
What should happen if you try to set an out of range value on an enum in the DOM w3c/svgwg#423 (2 comments by @AmeliaBR, @boggydigital)
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (2 comments by @boggydigital, @css-meeting-bot)
-
The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. w3c/svgwg#297 (1 comment by @boggydigital)
-
Make URL-resolution compatible with web components shadow DOM w3c/svgwg#466 (1 comment by @boggydigital)
-
stacking context / rendering order requirements are mostly not Web compatible w3c/svgwg#463 (1 comment by @boggydigital)
-
SVG...List.removeItem not specified to reserialize to attribute w3c/svgwg#461 (1 comment by @boggydigital)
-
Clean up assets once all removals/referments from SVG2 are merged w3c/svgwg#454 (1 comment by @boggydigital)
-
Move corresponding[Use]Element members to main SVGElement definition? w3c/svgwg#440 (1 comment by @boggydigital)
-
Do we really need not to reflect additional enum values in SVG 2 w3c/svgwg#424 (1 comment by @boggydigital)
-
context-value UA rules for OpenType are giving unexpected rendering / compat problems w3c/svgwg#421 (1 comment by @boggydigital)
-
Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit w3c/svgwg#419 (1 comment by @boggydigital)
-
Does the entire path need to be valid in order to use a path attribute on a textPath w3c/svgwg#393 (1 comment by @boggydigital)
-
Review of L.2.1 changes across the whole document - status w3c/svgwg#392 (1 comment by @boggydigital)
-
SVGTextPathElement interface seems to be missing properties w3c/svgwg#391 (1 comment by @boggydigital)
-
Support HTML metadata elements in both HTML and SVG namespaces? w3c/svgwg#388 (1 comment by @boggydigital)
-
'pathLength' interaction with <textPath> with a percentage 'startOffset' w3c/svgwg#383 (1 comment by @boggydigital)
-
Make textLength property on <text> and <tspan> a styleable property w3c/svgwg#375 (1 comment by @boggydigital)
-
SVG2 spec means elements within a <use> tag can not be targeted for styling w3c/svgwg#367 (1 comment by @boggydigital)
-
Remove Paths additions that were copied to SVG Paths specification w3c/svgwg#364 (1 comment by @boggydigital)
-
'image' element not defined to fire 'load' event when load happens w3c/svgwg#361 (1 comment by @boggydigital)
-
Clean up definitions around transforms on root SVG element w3c/svgwg#360 (1 comment by @boggydigital)
-
Reserialization of SVGStringList for comma-separated values w3c/svgwg#351 (1 comment by @boggydigital)
-
Resolved value for the 'width' and 'height' geometry properties w3c/svgwg#349 (1 comment by @boggydigital)
-
Allow setting the SVG context properties when in an HTML <img> tag w3c/svgwg#348 (1 comment by @boggydigital)
-
Enhance `<pattern>` to support auto-width or auto-height for pattern tiles with a `viewBox` w3c/svgwg#342 (1 comment by @boggydigital)
-
Add a method to return the path direction (tangent) angle at a given distance w3c/svgwg#338 (1 comment by @boggydigital)
-
Show need for "segment-completing closepath" with curves/arcs w3c/svgwg#336 (1 comment by @boggydigital)
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335 (1 comment by @boggydigital)
-
Shorthand properties should be promoted to presentation attributes. w3c/svgwg#334 (1 comment by @boggydigital)
-
overflow="auto" should be treated as hidden rather than visible w3c/svgwg#329 (1 comment by @boggydigital)
-
SVG should specify what CSS attribute selectors and class selectors match on w3c/svgwg#328 (1 comment by @boggydigital)
-
SVGTransform's setMatrix method should take a DOMMatrix2DInit w3c/svgwg#326 (1 comment by @boggydigital)
-
grammar for "closepath can substitute for final coordinate" is broken w3c/svgwg#325 (1 comment by @boggydigital)
-
C.4.2 out-of-range flag values note is invalid/unsupported, should be dropped w3c/svgwg#324 (1 comment by @boggydigital)
-
How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties w3c/svgwg#323 (1 comment by @boggydigital)
-
Remove un-implemented `pointer-events` "painted" rules for images w3c/svgwg#322 (1 comment by @boggydigital)
-
`text-anchor` not well specified for negative character advance w3c/svgwg#317 (1 comment by @boggydigital)
-
SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString w3c/svgwg#315 (1 comment by @boggydigital)
-
getPathSegAtLength had consistent implementation behavior for invalid paths w3c/svgwg#313 (1 comment by @boggydigital)
-
Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec w3c/svgwg#309 (1 comment by @boggydigital)
-
getScreenCTM (and friends?) results for elements that are not in the rendering tree? w3c/svgwg#307 (1 comment by @boggydigital)
-
patternTransform browser implementations do not match spec w3c/svgwg#293 (1 comment by @boggydigital)
-
Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript w3c/svgwg#291 (1 comment by @boggydigital)
-
Define how <image> and <img> deal with width & height, and media queries w3c/svgwg#289 (1 comment by @boggydigital)
-
Mixed content issue when viewing GitHub-hosted spec over HTTPS w3c/svgwg#283 (1 comment by @boggydigital)
-
Clarify behaviour of getPointAtLength() and getPathSegmentAtLength() at discontinuities. w3c/svgwg#282 (1 comment by @boggydigital)
-
Consider adding a switch to control how Addresssable Characters are treated w3c/svgwg#280 (1 comment by @boggydigital)
-
TextPath for zero length single closed path causes division by zero w3c/svgwg#272 (1 comment by @boggydigital)
-
-
6 pull requests opened.
-
remove redundant words w3c/svgwg#477, by @prlbr.
-
Textpath pathlength w3c/svgwg#476, by @Tavmjong.
-
Remove left-over references to solid-color and solid-opacity w3c/svgwg#475, by @BigBadaboom.
-
Fix reference for isolation property w3c/svgwg#473, by @ewilligers.
-
Remove unneeded 'shape-outside' definition. Fixes #288. w3c/svgwg#471, by @Tavmjong.
-
Update web-platform-tests URLs w3c/svgwg#470, by @foolip.
-
-
4 pull requests merged.
-
Fix reference for isolation property w3c/svgwg#473.
-
Remove unneeded 'shape-outside' definition. Fixes #288. w3c/svgwg#471.
-
Update web-platform-tests URLs w3c/svgwg#470.
-
Use stretchy parentheses for the arctan argument. w3c/svgwg#327.
-
-
3 pull requests received 5 new comments.
-
Use stretchy parentheses for the arctan argument. w3c/svgwg#327 (3 comments by @fred-wang, @liamquin)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
5 issues opened in the SVG Accessibility Task Force.
-
Please clarify group role w3c/aria#786, by @prlbr.
-
Scrollbar aria-orientation required property? w3c/aria#780, by @iannightingale.
-
Consider treating nameless forms similar to nameless regions w3c/aria#778, by @joanmarie.
-
-
7 issues closed in the SVG Accessibility Task Force.
-
Tree: confusing definition w3c/aria#764.
-
Role parity for html:blockquote, html:cite, html:q w3c/aria#528.
-
HTML blockquote w3c/aria#476.
-
ARIA role for HTML p w3c/aria#474.
-
14 issues in the SVG Accessibility Task Force received 35 new comments.
-
Scrollbar aria-orientation required property? w3c/aria#780 (14 comments by @jnurthen, @joanmarie, @katiehockman)
-
Clarify whether alt attribute is valid alternative text for role="img" w3c/aria#783 (6 comments by @carmacleod, @jnurthen)
-
for attribute of label with matching ID attribute of aria widget w3c/aria#707 (2 comments by @carmacleod, @jnurthen)
-
Clarify whether owned-by author rules need explicit role attributes w3c/aria#772 (2 comments by @jnurthen, @sideshowbarker)
-
Bringing user "actions" to the web (similar to VoiceOver and Switch Control custom actions) w3c/aria#762 (1 comment by @mcking65)
-
ARIA 1.2: Explicit guidance needed for non-pertinent errormessage elements w3c/aria#587 (1 comment by @mcking65)
-
define aria attributes that include a human readable text string are translatable attributes w3c/aria#755 (1 comment by @jnurthen)
-
Consider moving normative, NON-mapping content from Core AAM to ARIA w3c/aria#779 (1 comment by @joanmarie)
-
Consider treating nameless forms similar to nameless regions w3c/aria#778 (1 comment by @stevefaulkner)
-
-
4 pull requests opened in the SVG Accessibility Task Force.
-
Issue737 menuitem and groups w3c/aria#784, by @jnurthen.
-
Issue719 allow group in listbox w3c/aria#782, by @jnurthen.
-
2 pull requests merged in the SVG Accessibility Task Force.
-
fix #764 w3c/aria#766.
-
1 pull request closed in the SVG Accessibility Task Force.
-
3 pull requests in the SVG Accessibility Task Force received 6 new comments.
-
Move Aria Orientation on scrollbar to supported section (from required) w3c/aria#781 (3 comments by @jnurthen, @joanmarie)
-
Clarify whether alt attribute is valid alternative text for role="img… w3c/aria#785 (2 comments by @jnurthen, @mcking65)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
56 issues opened in the SVG Accessibility Task Force.
-
Need clarity on missing/invalid ARIA attribute values w3c/aria#777, by @minorninth.
-
aria-controls a required property for Combobox? w3c/aria#776, by @cpandhi.
-
Is aria-controls a required properties for Combobox? w3c/aria#775, by @cpandhi.
-
Tristate value type: the default value should be "undefined" w3c/aria#773, by @aristov.
-
Authoring Practices, navigation w3c/aria#770, by @rbeezer.
-
Authoring Practices, sub-regions? w3c/aria#769, by @rbeezer.
-
"Step 3" of Authoring Practices w3c/aria#768, by @rbeezer.
-
Consider addition of property(ies) to expose braille string w3c/aria#765, by @joanmarie.
-
Tree: confusing definition w3c/aria#764, by @aristov.
-
Allow role status/alert for noscript? w3c/aria#763, by @Malvoz.
-
Add role="image" as synonym for role="img" w3c/aria#758, by @jnurthen.
-
Clarify use of aria-label on elements with no role w3c/aria#756, by @jnurthen.
-
explore whether to have expandable columns w3c/aria#754, by @jnurthen.
-
Role Extensibility w3c/aria#753, by @jnurthen.
-
Work on getting AT to follow pronunciation hints w3c/aria#752, by @jnurthen.
-
Expand value types for aria-invalid w3c/aria#751, by @jnurthen.
-
Creation of resource definitions for localized state information w3c/aria#750, by @jnurthen.
-
Annotations w3c/aria#749, by @jnurthen.
-
Support selectors in ARIA relationships w3c/aria#745, by @jnurthen.
-
Consider removing aria-level from grid w3c/aria#743, by @jnurthen.
-
role for Semantic Zoom w3c/aria#740, by @jnurthen.
-
Clarify aria-hidden=false w3c/aria#736, by @jnurthen.
-
Harmonize role / state / property cross reference format w3c/aria#734, by @michael-n-cooper.
-
aria-hidden content misleading w3c/aria#731, by @jnurthen.
-
Introduce role="key" w3c/aria#730, by @jnurthen.
-
The Roles model introduces a potential timing problem w3c/aria#729, by @jnurthen.
-
reword or remove excess notes in #aria-hidden w3c/aria#726, by @jnurthen.
-
Move abstract roles out of main spec w3c/aria#725, by @michael-n-cooper.
-
Set up links to APG for each feature w3c/aria#723, by @michael-n-cooper.
-
Add aria-expanded as a supported property of listbox w3c/aria#722, by @joanmarie.
-
Add aria-valuetext as a supported property of listbox w3c/aria#721, by @joanmarie.
-
role:nameFrom needs "unsupported" value w3c/aria#720, by @joanmarie.
-
-
34 issues closed in the SVG Accessibility Task Force.
-
accname-aam clarify hidden w3c/aria#658.
-
Is aria-controls a required properties for Combobox? w3c/aria#775.
-
Authoring Practices, navigation w3c/aria#770.
-
Authoring Practices, sub-regions? w3c/aria#769.
-
"Step 3" of Authoring Practices w3c/aria#768.
-
Add ARIA property string reflection on Element w3c/aria#691.
-
CSS AAM: docs with layout/read order issues w3c/aria#383.
-
WCAG/ACCNAME discrepancy with `<img alt="" title="foo"> w3c/aria#602.
-
accname-aam need to clarify aria-owns in Step 2F w3c/aria#538.
-
Tab panel doesn't use role=application, but example does w3c/aria#415.
-
How to use the taxonomy to extend roles effectively w3c/aria#208.
-
How the ¨tying together script¨ works w3c/aria#210.
-
When casing is relevant, casing preferences w3c/aria#211.
-
Which pieces need to be filled in to trigger script w3c/aria#214.
-
Role name patterns w3c/aria#207.
-
Allow role status/alert for noscript? w3c/aria#763.
-
WAI-ARIA 1.1: base concepts link to HTML 4 w3c/aria#129.
-
HTML <div> and <span> w3c/aria#478.
-
[ROLE PARITY] "generic" role for div, span, br, etc. w3c/aria#525.
-
-
47 issues in the SVG Accessibility Task Force received 95 new comments.
-
[ROLE PARITY] "generic" role for div, span, br, etc. w3c/aria#525 (17 comments by @asurkov, @carmacleod, @devarshipant, @joanmarie, @jongund)
-
Need clarity on missing/invalid ARIA attribute values w3c/aria#777 (6 comments by @jnurthen, @minorninth, @stevefaulkner)
-
ARIA: should there be a password role? w3c/aria#166 (6 comments by @jnurthen, @johnfoliot, @LJWatson)
-
Bringing user "actions" to the web (similar to VoiceOver and Switch Control custom actions) w3c/aria#762 (5 comments by @jamesalley, @jnurthen, @juandopazo, @mcking65)
-
Clarify whether owned-by author rules need explicit role attributes w3c/aria#772 (4 comments by @joanmarie, @mcking65, @michael-n-cooper, @sideshowbarker)
-
Consider adding context attribute through which ATs could ensure correct presentation of content w3c/aria#767 (3 comments by @joanmarie, @johnfoliot)
-
Proposal for new aria-hint property. (Previously proposed as @aria-help) w3c/aria#739 (3 comments by @carmacleod, @jnurthen, @johnfoliot)
-
Is aria-controls a required properties for Combobox? w3c/aria#775 (2 comments by @carmacleod, @cpandhi)
-
Accessible name calc doesn't clearly say what happens with invalid reference or empty w3c/aria#515 (1 comment by @jnurthen)
-
Revisit normative ref to ui events keyboardevent key values when it hits rec w3c/aria#738 (1 comment by @jnurthen)
-
role combobox either misses text or is incorrect regarding role searchbox w3c/aria#742 (1 comment by @plweil)
-
CORE-AAM: Add conditional platform mappings for nameless forms w3c/aria#514 (1 comment by @jnurthen)
-
Core-AAM: Need to verify, expand upon, and/or correct AX API aria-activedescendant exposure w3c/aria#598 (1 comment by @jnurthen)
-
Core AAM: Clarify expectations regarding implementation of IAccessible::accSelect() w3c/aria#612 (1 comment by @jnurthen)
-
[AccName AAM] reinforcing "name" vs "description", split out algorithm into two w3c/aria#544 (1 comment by @jnurthen)
-
AccName-AAM: Include title attribute (as part of description computation) in Text Alternative Computation w3c/aria#584 (1 comment by @jnurthen)
-
w3c/aria#76 (1 comment by @jnurthen)
-
w3c/aria#74 (1 comment by @jnurthen)
-
Creation of resource definitions for localized state information w3c/aria#750 (1 comment by @jnurthen)
-
aria-relevant: find real-world use cases, consider deprecating it w3c/aria#712 (1 comment by @Iz-a11y)
-
Clarify that aria-multiline should not be changed on the fly because it impacts role mapping w3c/aria#727 (1 comment by @carmacleod)
-
ACCNAME-AAM: no mention of aria-placeholder in name/description calculation algorthim w3c/aria#337 (1 comment by @joanmarie)
-
method to determine how blocks of text are separated (aria-text separation (property)) w3c/aria#699 (1 comment by @joanmarie)
-
[ROLE PARITY] Verify we do NOT need new roles for these elements which already have roles w3c/aria#694 (1 comment by @joanmarie)
-
[ROLE PARITY] Verify we do NOT need new roles for these "not mapped" elements w3c/aria#693 (1 comment by @joanmarie)
-
-
4 pull requests opened in the SVG Accessibility Task Force.
-
Tristate value type: the default value should be "undefined" w3c/aria#774, by @aristov.
-
Add blockquote, caption, and paragraph roles w3c/aria#761, by @joanmarie.
-
Add blockquote, caption, footer, header, and paragraph roles w3c/aria#718, by @joanmarie.
-
-
2 pull requests merged in the SVG Accessibility Task Force.
-
Add blockquote, caption, and paragraph roles w3c/aria#761.
-
IDL attribute reflection branch w3c/aria#708.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
4 pull requests in the SVG Accessibility Task Force received 10 new comments.
-
Add blockquote, caption, footer, header, and paragraph roles w3c/aria#718 (4 comments by @carmacleod, @joanmarie, @prlbr)
-
TR publications
-
1 document published.
-
SVG Accessibility API Mappings published as a Working Draft. History of SVG Accessibility API Mappings
-
Participants
-
1 organization left.
-
Ministerio do Planejamento Orcamento e Gestao left.
-
GitHub
w3c/svgwg
-
14 issues opened.
-
Make URL-resolution compatible with web components shadow DOM w3c/svgwg#466, by @AmeliaBR.
-
Define "context" for SVG-in-OpenType glyphs w3c/svgwg#462, by @AmeliaBR.
-
SVG...List.removeItem not specified to reserialize to attribute w3c/svgwg#461, by @fsoder.
-
Definitions not marked as export w3c/svgwg#459, by @dirkschulze.
-
isPointInFill/isPointInStroke and display: none and other specifics w3c/svgwg#456, by @dirkschulze.
-
Clean up assets once all removals/referments from SVG2 are merged w3c/svgwg#454, by @dstorey.
-
Identify SVG1 elements that are obsolete in SVG2 w3c/svgwg#448, by @boggydigital.
-
Computed value for white-space incorrect? w3c/svgwg#447, by @dstorey.
-
Consider adding decoding and decode to SVGImageElement w3c/svgwg#444, by @dstorey.
-
Number syntax: digit-sequence "." w3c/svgwg#442, by @dirkschulze.
-
Move corresponding[Use]Element members to main SVGElement definition? w3c/svgwg#440, by @dstorey.
-
Harmonise inline-size with CSS Logical properties w3c/svgwg#436, by @dstorey.
-
-
20 issues closed.
-
Computed value for white-space incorrect? w3c/svgwg#447.
-
Definitions not marked as export w3c/svgwg#459.
-
Add a presentation attribute for `paint-order` w3c/svgwg#316.
-
Clarify relation of isPointInFill and pointer-events w3c/svgwg#416.
-
Consider adding decoding and decode to SVGImageElement w3c/svgwg#444.
-
SVG Integration: mixed content w3c/svgwg#357.
-
SVG Integration: update "This version" link w3c/svgwg#356.
-
Number syntax: digit-sequence "." w3c/svgwg#442.
-
SVG MIME Type (image/svg+xml) is misleading to developers w3c/svgwg#266.
-
Update percentage types to the new convenience notations w3c/svgwg#190.
-
Please link to GitHub from the drafts w3c/svgwg#355.
-
Should SVG 2 switch to Bikeshed? w3c/svgwg#73.
-
SVG and CSS transform w3c/svgwg#318.
-
32 issues received 83 new comments.
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (8 comments by @dirkschulze, @fsoder, @fuchsia, @longsonr)
-
context-value UA rules for OpenType are giving unexpected rendering / compat problems w3c/svgwg#421 (6 comments by @AmeliaBR, @svgeesus)
-
Consider adding decoding and decode to SVGImageElement w3c/svgwg#444 (6 comments by @dstorey, @fsoder, @progers)
-
Do we really need not to reflect additional enum values in SVG 2 w3c/svgwg#424 (6 comments by @BigBadaboom, @css-meeting-bot, @dstorey, @longsonr)
-
Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript w3c/svgwg#291 (6 comments by @dstorey, @longsonr)
-
Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint w3c/svgwg#389 (4 comments by @dirkschulze, @dstorey, @longsonr)
-
SVGTransform's setMatrix method should take a DOMMatrix2DInit w3c/svgwg#326 (4 comments by @dirkschulze, @dstorey, @zcorpan)
-
Define "context" for SVG-in-OpenType glyphs w3c/svgwg#462 (3 comments by @AmeliaBR, @svgeesus, @Tavmjong)
-
SVG MIME Type (image/svg+xml) is misleading to developers w3c/svgwg#266 (3 comments by @06b, @dstorey, @paragonie-scott)
-
Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec w3c/svgwg#309 (3 comments by @dirkschulze, @dstorey, @foolip)
-
stacking context / rendering order requirements are mostly not Web compatible w3c/svgwg#463 (2 comments by @AmeliaBR, @heycam)
-
isPointInFill/isPointInStroke and display: none and other specifics w3c/svgwg#456 (2 comments by @AmeliaBR, @dirkschulze)
-
Marker element percentages are missing reference values w3c/svgwg#64 (2 comments by @AmeliaBR, @dstorey)
-
Move corresponding[Use]Element members to main SVGElement definition? w3c/svgwg#440 (2 comments by @AmeliaBR, @dstorey)
-
Allow more properties to be applied on <a> inside <text> w3c/svgwg#401 (2 comments by @dstorey, @jarek-foksa)
-
Allow setting the SVG context properties when in an HTML <img> tag w3c/svgwg#348 (1 comment by @AmeliaBR)
-
Clarify how user agents should implement vendor-specific extensions w3c/svgwg#53 (1 comment by @dstorey)
-
Update SVG WG Feedback page on w3.org to point to GitHub issues w3c/svgwg#216 (1 comment by @dstorey)
-
Can we remove presentation attribute / element table from Attribute Index appendix? w3c/svgwg#83 (1 comment by @dstorey)
-
-
25 pull requests opened.
-
Export text content element definition w3c/svgwg#465, by @dirkschulze.
-
Remove defintion of white-space w3c/svgwg#464, by @dstorey.
-
Update data-export w3c/svgwg#460, by @dstorey.
-
Remove unused defs and fix some linking issues w3c/svgwg#458, by @dstorey.
-
Fix issue with MathML namespace and duplicate ID in changelog w3c/svgwg#457, by @dstorey.
-
Remove SVGCursorElement... w3c/svgwg#455, by @dstorey.
-
Remove SVGCursorElement w3c/svgwg#453, by @dstorey.
-
Remove mesh gradients w3c/svgwg#452, by @dstorey.
-
Remove hatch gradients w3c/svgwg#451, by @dstorey.
-
Remove solidcolour w3c/svgwg#450, by @dstorey.
-
Update property index w3c/svgwg#446, by @dstorey.
-
Allow paint-order to be a presentational attribute w3c/svgwg#445, by @dstorey.
-
Add myself to editors w3c/svgwg#441, by @dstorey.
-
Fix broken and missing references w3c/svgwg#439, by @dstorey.
-
Fixes #356 this version link on Integration spec w3c/svgwg#437, by @dstorey.
-
Add GitHub link to Integration and Template w3c/svgwg#435, by @dstorey.
-
Update <length> | <percentage> to <length-percentage> w3c/svgwg#434, by @dstorey.
-
Make DOMPointInit argument optional according to WebIDL spec. w3c/svgwg#433, by @dirkschulze.
-
Fix #402 Use CCS Colour L4 definition for computed value of *-opacity w3c/svgwg#432, by @dstorey.
-
Fix #403 update opacity-value to alpha-value w3c/svgwg#431, by @dstorey.
-
Fixes #405 update description of when visibility applies w3c/svgwg#430, by @dstorey.
-
Fix lint/build issues w3c/svgwg#429, by @dstorey.
-
Update spec references for HTML, DOM and CSSOM w3c/svgwg#428, by @dstorey.
-
-
25 pull requests merged.
-
Export text content element definition w3c/svgwg#465.
-
Remove solidcolour w3c/svgwg#450.
-
Remove defintion of white-space w3c/svgwg#464.
-
Update data-export w3c/svgwg#460.
-
Remove unused defs and fix some linking issues w3c/svgwg#458.
-
Remove SVGCursorElement... w3c/svgwg#455.
-
Remove hatch gradients w3c/svgwg#451.
-
Remove mesh gradients w3c/svgwg#452.
-
Allow paint-order to be a presentational attribute w3c/svgwg#445.
-
Fixes #356 this version link on Integration spec w3c/svgwg#437.
-
Add myself to editors w3c/svgwg#441.
-
Fix broken and missing references w3c/svgwg#439.
-
Update <length> | <percentage> to <length-percentage> w3c/svgwg#434.
-
Add GitHub link to Integration and Template w3c/svgwg#435.
-
Fix #403 update opacity-value to alpha-value w3c/svgwg#431.
-
Fix lint/build issues w3c/svgwg#429.
-
Use DOMPointInit argument for getCharNumAtPosition. #389 w3c/svgwg#414.
-
Update spec references for HTML, DOM and CSSOM w3c/svgwg#428.
-
Add DocumentAndElementEventHandlers w3c/svgwg#413.
-
Add or update dfns for definitions w3c/svgwg#425.
-
-
1 pull request closed.
-
Remove SVGCursorElement w3c/svgwg#453.
-
-
17 pull requests received 69 new comments.
-
Update <length> | <percentage> to <length-percentage> w3c/svgwg#434 (19 comments by @AmeliaBR, @dirkschulze, @dstorey)
-
Use DOMPointInit argument for getCharNumAtPosition. #389 w3c/svgwg#414 (3 comments by @dirkschulze, @dstorey)
-
Fixes #405 update description of when visibility applies w3c/svgwg#430 (2 comments by @AmeliaBR, @dstorey)
-
Fix #402 Use CCS Colour L4 definition for computed value of *-opacity w3c/svgwg#432 (2 comments by @dirkschulze, @dstorey)
-
GitHub
w3c/svgwg
-
20 issues opened.
-
Clarify hit testing behavior of <foreignObject> w3c/svgwg#427, by @chrishtr.
-
Do we really need not to reflect additional enum values in SVG 2 w3c/svgwg#424, by @longsonr.
-
Bounding box algorithm is not precise w3c/svgwg#422, by @dirkschulze.
-
Start using URL (instead of URI reference) w3c/svgwg#420, by @annevk.
-
Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit w3c/svgwg#419, by @dirkschulze.
-
Use <dfn> for definitions w3c/svgwg#417, by @fantasai.
-
Clarify relation of isPointInFill and pointer-events w3c/svgwg#416, by @dirkschulze.
-
Do we need to replace DOMStringMap? w3c/svgwg#412, by @dirkschulze.
-
Deprecate type attribute on SVGStyleElement? w3c/svgwg#411, by @dstorey.
-
Update SVGScriptElement and SVGImageElement to use src? w3c/svgwg#410, by @dstorey.
-
Typo in viewBox attribute type definition w3c/svgwg#407, by @jarek-foksa.
-
Wrong description of percentage units w3c/svgwg#406, by @jarek-foksa.
-
Wrong description of "visibility" property w3c/svgwg#405, by @jarek-foksa.
-
Remove "style attributes" from all element definitions w3c/svgwg#404, by @jarek-foksa.
-
Replace <opacity-value> with <alpha-value> w3c/svgwg#403, by @jarek-foksa.
-
Allow more properties to be applied on <a> inside <text> w3c/svgwg#401, by @jarek-foksa.
-
-
8 issues closed.
-
Do we need to replace DOMStringMap? w3c/svgwg#412.
-
Update WebIDL definition(s) to use new mixin syntax w3c/svgwg#353.
-
Typo in viewBox attribute type definition w3c/svgwg#407.
-
"mode" of a shadow root which <use> element uses is unclear w3c/svgwg#396.
-
Remove "text content child element" category w3c/svgwg#399.
-
Add <a> to "text content element" category w3c/svgwg#400.
-
26 issues received 91 new comments.
-
Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint w3c/svgwg#389 (13 comments by @BigBadaboom, @css-meeting-bot, @dirkschulze, @tabatkins)
-
Make SVGAnimatedX data types extend DOMX data types wherever possible w3c/svgwg#175 (11 comments by @AmeliaBR, @dstorey, @longsonr, @travisleithead)
-
Do we really need not to reflect additional enum values in SVG 2 w3c/svgwg#424 (5 comments by @dirkschulze, @longsonr)
-
Clarify relation of isPointInFill and pointer-events w3c/svgwg#416 (4 comments by @AmeliaBR, @dirkschulze)
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335 (3 comments by @AmeliaBR, @fuchsia)
-
How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties w3c/svgwg#323 (3 comments by @AmeliaBR, @dirkschulze, @Fuzzyma)
-
Browsers do not implement transform attribute syntax as described by w3c w3c/svgwg#426 (3 comments by @AmeliaBR, @longsonr)
-
Rename SVGBoundingBoxOptions to SVGBoundingBoxOptionsInit w3c/svgwg#419 (3 comments by @dirkschulze, @dstorey)
-
context-value UA rules for OpenType are giving unexpected rendering / compat problems w3c/svgwg#421 (3 comments by @AmeliaBR, @upsuper)
-
Update SVGScriptElement and SVGImageElement to use src? w3c/svgwg#410 (3 comments by @AmeliaBR, @dstorey, @prlbr)
-
Deprecate type attribute on SVGStyleElement? w3c/svgwg#411 (3 comments by @AmeliaBR, @dirkschulze, @dstorey)
-
Start using URL (instead of URI reference) w3c/svgwg#420 (2 comments by @css-meeting-bot, @dirkschulze)
-
The computed value of fill-opacity and stroke-opacity should never be a percentage w3c/svgwg#402 (2 comments by @AmeliaBR, @longsonr)
-
-
7 pull requests opened.
-
Add or update dfns for definitions w3c/svgwg#425, by @dstorey.
-
Keep the linting minions happy w3c/svgwg#418, by @dstorey.
-
Add HTMLOrSVGElement mixn w3c/svgwg#415, by @dstorey.
-
Use DOMPointInit argument for getCharNumAtPosition. #389 w3c/svgwg#414, by @dirkschulze.
-
Add DocumentAndElementEventHandlers w3c/svgwg#413, by @dstorey.
-
Update SVGAElement to match attributes on HTMLAnchorElement w3c/svgwg#409, by @dstorey.
-
Fixes #407 copy-pasto in viewBox definition w3c/svgwg#408, by @dstorey.
-
-
6 pull requests merged.
-
Keep the linting minions happy w3c/svgwg#418.
-
Add HTMLOrSVGElement mixn w3c/svgwg#415.
-
Fixes #407 copy-pasto in viewBox definition w3c/svgwg#408.
-
Revisions to sentence on focusable elements w3c/svgwg#158.
-
-
2 pull requests closed.
-
Change SVGMeshElement to derive from SVGGraphicsElement w3c/svgwg#311.
-
-
12 pull requests received 52 new comments.
-
Remove support for segment-completing close path w3c/svgwg#398 (4 comments by @css-meeting-bot, @dirkschulze, @ewilligers)
-
Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 w3c/svgwg#376 (4 comments by @AmeliaBR, @dirkschulze, @dstorey, @tobie)
-
Use DOMPointInit argument for getCharNumAtPosition. #389 w3c/svgwg#414 (2 comments by @AmeliaBR, @dirkschulze)
-
Update SVGAElement to match attributes on HTMLAnchorElement w3c/svgwg#409 (2 comments by @dirkschulze, @dstorey)
-
Add text-transform property to the list of required CSS properties w3c/svgwg#251 (2 comments by @boggydigital, @css-meeting-bot)
-
Change SVGMeshElement to derive from SVGGraphicsElement w3c/svgwg#311 (1 comment by @css-meeting-bot)
w3c/svg-aam
-
1 issue opened.
-
Fix issues with mapping script w3c/svg-aam#10, by @AmeliaBR.
-
-
1 issue received 5 new comments.
SVG Accessibility Task Force
GitHub
w3c/aria
-
9 issues opened in the SVG Accessibility Task Force.
-
Confusing sentence in presentation role discussion w3c/aria#717, by @carmacleod.
-
Broken link: states and properties w3c/aria#714, by @hidde.
-
Why is toolbar as a document structure role? w3c/aria#713, by @Jinjiang.
-
aria-relevant: find real-world use cases, consider deprecating it w3c/aria#712, by @aleventhal.
-
aria-valuetext would be useful on many more roles w3c/aria#711, by @jnurthen.
-
Is the use of the word "node" correct in aria-atomic w3c/aria#709, by @DavidMacDonald.
-
-
1 issue closed in the SVG Accessibility Task Force.
-
7 issues in the SVG Accessibility Task Force received 20 new comments.
-
aria-relevant: find real-world use cases, consider deprecating it w3c/aria#712 (8 comments by @accdc, @aleventhal, @DavidMacDonald, @devarshipant)
-
Add ARIA property string reflection on Element w3c/aria#691 (4 comments by @carmacleod, @cookiecrook)
-
concatenate non identical sources for ACCNAME and AccDescription Computation w3c/aria#715 (1 comment by @joanmarie)
-
-
1 pull request opened in the SVG Accessibility Task Force.
-
IDL attribute reflection branch w3c/aria#708, by @cookiecrook.
-
-
1 pull request in the SVG Accessibility Task Force received 6 new comments.
GitHub
w3c/svgwg
-
9 issues opened.
-
Add <a> to "text content element" category w3c/svgwg#400, by @jarek-foksa.
-
Remove "text content child element" category w3c/svgwg#399, by @jarek-foksa.
-
"mode" of a shadow root which <use> element uses is unclear w3c/svgwg#396, by @hayatoito.
-
Should we move more HTMLElement members to HTMLorSVGElement mixin? w3c/svgwg#395, by @dstorey.
-
dur attribute should permit leading . w3c/svgwg#394, by @longsonr.
-
Review of L.2.1 changes across the whole document - status w3c/svgwg#392, by @liamquin.
-
SVGTextPathElement interface seems to be missing properties w3c/svgwg#391, by @longsonr.
-
SVG 1.1 Errata: How to Proceed? w3c/svgwg#390, by @AmeliaBR.
-
-
1 issue closed.
-
Add [Exposed] to all interfaces w3c/svgwg#345.
-
-
10 issues received 46 new comments.
-
Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint w3c/svgwg#389 (13 comments by @AmeliaBR, @css-meeting-bot, @domenic, @fsoder, @longsonr, @progers, @tabatkins)
-
SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString w3c/svgwg#315 (10 comments by @css-meeting-bot, @dstorey, @liamquin)
-
Should we move more HTMLElement members to HTMLorSVGElement mixin? w3c/svgwg#395 (7 comments by @AmeliaBR, @css-meeting-bot, @dstorey, @tabatkins)
-
Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement w3c/svgwg#60 (7 comments by @AmeliaBR, @annevk, @css-meeting-bot, @domenic, @dstorey)
-
Implicit and allowed roles for SVG element in a HTML document w3c/svgwg#372 (3 comments by @AmeliaBR, @dstorey)
-
Does the entire path need to be valid in order to use a path attribute on a textPath w3c/svgwg#393 (1 comment by @AmeliaBR)
-
-
2 pull requests opened.
-
Remove support for segment-completing close path w3c/svgwg#398, by @ewilligers.
-
Remove path rotation requirement w3c/svgwg#397, by @ewilligers.
-
-
2 pull requests merged.
-
Remove path rotation requirement w3c/svgwg#397.
-
Fixes #345 Add [Exposed] to SVG interfaces w3c/svgwg#387.
-
-
2 pull requests received 16 new comments.
-
Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 w3c/svgwg#376 (14 comments by @AmeliaBR, @cynthia, @dstorey, @tobie)
-
w3c/svg-aam
-
4 issues opened.
-
Consider replacing Glossary with a link to ARIA w3c/svg-aam#9, by @AmeliaBR.
-
Exposing SVG view behavior and viewTarget to accessibility APIs w3c/svg-aam#8, by @AmeliaBR.
-
Harmonize use-element behavior with other shadow DOM behavior w3c/svg-aam#7, by @AmeliaBR.
-
Should structured descriptions be exposed in the accessibility tree? w3c/svg-aam#6, by @AmeliaBR.
-
-
4 issues closed.
-
Consider replacing Glossary with a link to ARIA w3c/svg-aam#9.
-
Add details about aria-roledescription usage w3c/svg-aam#5.
-
Add Ian Pouncey as new co-editor w3c/svg-aam#4.
-
-
4 issues received 9 new comments.
-
Should more mappings be based on Graphics ARIA roles rather than Core ARIA roles? w3c/svg-aam#1 (1 comment by @AmeliaBR)
SVG Accessibility Task Force
GitHub
w3c/aria
-
2 issues opened in the SVG Accessibility Task Force.
-
Slider: Specify a decimal value for valuenow, valuemin, valuemax w3c/aria#706, by @0ddfell0w.
-
2 issues in the SVG Accessibility Task Force received 16 new comments.
-
for attribute of label with matching ID attribute of aria widget w3c/aria#707 (15 comments by @accdc, @carmacleod, @devarshipant, @mcking65, @stes-acc, @stevefaulkner)
-
Slider: Specify a decimal value for valuenow, valuemin, valuemax w3c/aria#706 (1 comment by @carmacleod)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
13 issues opened in the SVG Accessibility Task Force.
-
Clarify aria-hidden wording w3c/aria#705, by @carmacleod.
-
default aria-valuenow for scrollbar w3c/aria#704, by @kbae00.
-
Boolean attribute oddity with relation to HTML5 w3c/aria#703, by @dead-claudia.
-
Latest rec link in 1.2 editor's draft points to 1.0 w3c/aria#701, by @mcking65.
-
Should aria-selected be listed as required for option role? w3c/aria#700, by @mcking65.
-
-
8 issues closed in the SVG Accessibility Task Force.
-
Latest rec link in 1.2 editor's draft points to 1.0 w3c/aria#701.
-
[DPUB] incorrect superclass for doc-pullquote w3c/aria#652.
-
[DPUB] subtitle name from contents w3c/aria#654.
-
[PR-dpub-aria-1.0-20171102] “illustratration” typo w3c/aria#656.
-
[PR-dpub-aria-1.0-20171102] example 34 typo w3c/aria#657.
-
-
1 issue reopened in the SVG Accessibility Task Force.
-
19 issues in the SVG Accessibility Task Force received 73 new comments.
-
Add ARIA property string reflection on Element w3c/aria#691 (28 comments by @alice, @asurkov, @carmacleod, @cookiecrook, @domenic)
-
[ROLE PARITY] Verify we do NOT need new roles for these "not mapped" elements w3c/aria#693 (8 comments by @cookiecrook, @domenic, @LJWatson)
-
[ROLE PARITY] Determine which of these elements with existing ARIA role mappings require a new role w3c/aria#696 (7 comments by @annevk, @cookiecrook, @domenic, @joanmarie)
-
[ROLE PARITY] Determine why these elements with ARIA roles have customized mappings for some platforms w3c/aria#695 (6 comments by @cookiecrook, @joanmarie)
-
method to determine how blocks of text are separated (aria-text separation (property)) w3c/aria#699 (4 comments by @cookiecrook, @joanmarie)
-
[ROLE PARITY] Determine if any of these mostly unmapped elements require a specific role w3c/aria#698 (3 comments by @domenic, @joanmarie)
-
[ROLE PARITY] Determine which of these mapped elements require a specific role, versus a generic role w3c/aria#697 (2 comments by @cookiecrook, @domenic)
-
some attributes are missing from states/props categorization section w3c/aria#702 (1 comment by @cookiecrook)
-
SVG-AAM: Identify elements which support aria-roledescription without an explicit or implicit role w3c/aria#599 (1 comment by @AmeliaBR)
-
[ROLE PARITY] Verify we do NOT need new roles for these elements which already have roles w3c/aria#694 (1 comment by @joanmarie)
-
DPUB-ARIA: doc-abstract's description has 'principle' where it should be 'principal' w3c/aria#692 (1 comment by @joanmarie)
-
TR publications
-
2 documents published.
-
Graphics Accessibility API Mappings published as a Working Draft. History of Graphics Accessibility API Mappings
-
WAI-ARIA Graphics Module published as a Working Draft. History of WAI-ARIA Graphics Module
-
GitHub
w3c/svgwg
-
4 issues opened.
-
Support HTML metadata elements in both HTML and SVG namespaces? w3c/svgwg#388, by @BigBadaboom.
-
Review implementation support - Paths chapter w3c/svgwg#385, by @ewilligers.
-
Review implementation support - Embedded Content chapter w3c/svgwg#384, by @ewilligers.
-
1 issue closed.
-
CMYK Support w3c/svgwg#343.
-
-
13 issues received 28 new comments.
-
Add a presentation attribute for `paint-order` w3c/svgwg#316 (6 comments by @AmeliaBR, @css-meeting-bot, @dstorey, @Tavmjong)
-
'pathLength' interaction with <textPath> with a percentage 'startOffset' w3c/svgwg#383 (6 comments by @AmeliaBR, @ewilligers, @fsoder, @longsonr)
-
Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript w3c/svgwg#291 (4 comments by @AmeliaBR, @css-meeting-bot, @longsonr)
-
Shouldn't getCharNumAtPosition take an argument of type DOMPointReadOnly rather than DOMPoint w3c/svgwg#389 (2 comments by @AmeliaBR, @longsonr)
-
Can we remove presentation attribute / element table from Attribute Index appendix? w3c/svgwg#83 (1 comment by @dstorey)
-
Make "show" widget in element definitions boxes play nicely with screen readers w3c/svgwg#110 (1 comment by @dstorey)
-
Support HTML metadata elements in both HTML and SVG namespaces? w3c/svgwg#388 (1 comment by @AmeliaBR)
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (1 comment by @fuchsia)
-
-
2 pull requests opened.
-
Fixes #345 Add [Exposed] to SVG interfaces w3c/svgwg#387, by @dstorey.
-
Paths: Remove bearing commands w3c/svgwg#386, by @ewilligers.
-
-
1 pull request merged.
-
Paths: Remove bearing commands w3c/svgwg#386.
-
w3c/svg-aam
-
3 issues opened.
-
Add details about aria-roledescription usage w3c/svg-aam#5, by @AmeliaBR.
-
Add Ian Pouncey as new co-editor w3c/svg-aam#4, by @AmeliaBR.
-
Prepare new working draft (February 2018) w3c/svg-aam#3, by @AmeliaBR.
-
-
1 issue reopened.
-
Add Ian Pouncey as new co-editor w3c/svg-aam#4, by @AmeliaBR.
-
-
2 issues received 4 new comments.
GitHub
w3c/svgwg
-
6 issues opened.
-
'pathLength' interaction with <textPath> with a percentage 'startOffset' w3c/svgwg#383, by @fsoder.
-
Excess parenthesis in text layout algorithm? ("Position on path" part) w3c/svgwg#382, by @fsoder.
-
Emojis and SVG <text> inconsistency w3c/svgwg#381, by @chaoaretasty.
-
SVG2 required properties excludes fill and stroke w3c/svgwg#380, by @svgeesus.
-
Where are unitless lengths allowed? What do they mean? w3c/svgwg#379, by @SimonSapin.
-
Mesh Patch in SVG2 is not C1 smooth at edge w3c/svgwg#377, by @wada314.
-
-
2 issues closed.
-
SVG2 required properties excludes fill and stroke w3c/svgwg#380.
-
Color chapter was trimmed down to CSS Color 3 and 4 refs w3c/svgwg#359.
-
-
10 issues received 28 new comments.
-
Where are unitless lengths allowed? What do they mean? w3c/svgwg#379 (12 comments by @dirkschulze, @heycam, @JeremiePat, @SimonSapin, @svgeesus)
-
Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript w3c/svgwg#291 (3 comments by @AmeliaBR, @foolip, @travisleithead)
-
Remove un-implemented `pointer-events` "painted" rules for images w3c/svgwg#322 (2 comments by @BigBadaboom)
-
-
1 pull request opened.
-
1 pull request merged.
-
Remove explicit currentColor from <paint> w3c/svgwg#304.
-
-
2 pull requests received 5 new comments.
-
'd' presentation attribute: use path() function w3c/svgwg#374 (4 comments by @AmeliaBR, @dirkschulze, @ewilligers, @fsoder)
-
w3c/svg-aam
-
2 issues opened.
-
TextPath and TSpan need platform-specific mappiings w3c/svg-aam#2, by @joanmarie.
-
-
1 issue received 4 new comments.
-
Should more mappings be based on Graphics ARIA roles rather than Core ARIA roles? w3c/svg-aam#1 (4 comments by @AmeliaBR, @joanmarie)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
6 issues opened in the SVG Accessibility Task Force.
-
Add ARIA property string reflection on Element w3c/aria#691, by @cookiecrook.
-
Consider a "token" role for next version w3c/aria#689, by @DavidMacDonald.
-
2 issues closed in the SVG Accessibility Task Force.
-
SVG-AAM: Corrections to platform mappings for ATK w3c/aria#133.
-
-
8 issues in the SVG Accessibility Task Force received 28 new comments.
-
Add ARIA property string reflection on Element w3c/aria#691 (16 comments by @alice, @asurkov, @carmacleod, @cookiecrook, @domenic, @rniwa)
-
SVG-AAM: Identify elements which support aria-roledescription without an explicit or implicit role w3c/aria#599 (4 comments by @accdc, @AmeliaBR)
-
Previous recommendation link https://www.w3.org/TR/wai-aria-1.0/ broken w3c/aria#687 (3 comments by @michael-n-cooper, @slauriat)
-
DPUB-ARIA: doc-abstract's description has 'principle' where it should be 'principal' w3c/aria#692 (1 comment by @mattgarrish)
-
ARIA 1.1: aria-expanded is not supported on menuitem roles w3c/aria#454 (1 comment by @sideshowbarker)
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
2 pull requests in the SVG Accessibility Task Force received 3 new comments.
-
one mapping-tables script that works with or without respec w3c/aria#499 (2 comments by @joanmarie, @michael-n-cooper)
-
Clarify that owned-by author rules need explicit role attributes w3c/aria#511 (1 comment by @sideshowbarker)
-