SVG Working Group - Activity in 2019
No matches.
GitHub
w3c/svgwg
-
9 issues opened.
-
Blob URL in SVG as references w3c/svgwg#769, by @upsuper.
-
Data URI in SVG Integration spec w3c/svgwg#768, by @upsuper.
-
Add circular arc path command 'R'. w3c/svgwg#767, by @tatarize.
-
8.2 equivalent transform of an SVG viewport, slight ambiguity. w3c/svgwg#766, by @tatarize.
-
Incorrect sweep-flag in circle/ellipse equivalent path w3c/svgwg#765, by @dalboris.
-
points-attribute: whitespaces and empty strings in SVG 1.1 vs SVG 2 w3c/svgwg#763, by @dalboris.
-
-
12 issues received 67 new comments.
-
Rect decomposition is invalid w3c/svgwg#753 (32 comments by @AmeliaBR, @BigBadaboom, @css-meeting-bot, @dalboris, @tatarize)
-
Change arc grammar to coordinates rather than numbers and flags. w3c/svgwg#755 (7 comments by @dalboris, @smfr, @tabatkins, @tatarize)
-
'Path' (entire path) vs. 'subpath' for markers on a start/end vertex of an open subpaths w3c/svgwg#759 (6 comments by @AmeliaBR, @BigBadaboom, @dalboris, @Doktorchen, @fsoder)
-
8.2 equivalent transform of an SVG viewport, slight ambiguity. w3c/svgwg#766 (3 comments by @gordonwoodhull, @tatarize)
-
points-attribute: whitespaces and empty strings in SVG 1.1 vs SVG 2 w3c/svgwg#763 (3 comments by @dalboris, @tabatkins)
-
Clarify that non-CSS rendering environments can override default width/height of embedded SVG w3c/svgwg#762 (3 comments by @AmeliaBR, @fsoder)
-
Third parameter of arc in path data should allow signed numbers w3c/svgwg#750 (1 comment by @dirkschulze)
-
-
2 pull requests opened.
-
Update links to SVG WG charter w3c/svgwg#761, by @jwatt.
-
Remove old/unused subdirectories from tools/ w3c/svgwg#760, by @jwatt.
-
-
3 pull requests merged.
-
Update links to SVG WG charter w3c/svgwg#761.
-
Remove old/unused subdirectories from tools/ w3c/svgwg#760.
-
Make the .gitignore patterns more robust, and simpler w3c/svgwg#758.
-
w3c/svg-aam
-
1 issue received 1 new comment.
-
Should structured descriptions be exposed in the accessibility tree? w3c/svg-aam#6 (1 comment by @medeaoblongata)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
10 issues opened in the SVG Accessibility Task Force.
-
Missing information for scrollbar? w3c/aria#1141, by @JAWS-test.
-
aria-roledescription should not be allowed on role generic w3c/aria#1140, by @scottaohara.
-
The aria-rowindex attribute being permitted on cells seems like a footgun w3c/aria#1138, by @bathos.
-
Aria-roledescription should not be a global attribute. w3c/aria#1132, by @accdc.
-
aria-roledescription should not duplicate the implicit or explicit role w3c/aria#1131, by @pkra.
-
aria-disabled non-focusable descendents w3c/aria#1130, by @WilcoFiers.
-
Request for aria-completed state w3c/aria#1126, by @medeaoblongata.
-
meter role should have optional aria-valuemin/max with defaults w3c/aria#1123, by @zcorpan.
-
-
17 issues in the SVG Accessibility Task Force received 43 new comments.
-
meter role should have optional aria-valuemin/max with defaults w3c/aria#1123 (7 comments by @carmacleod, @scottaohara, @zcorpan)
-
[Role Parity] What do we do about input (type=password)? w3c/aria#935 (6 comments by @annevk, @jnurthen, @johnfoliot, @LJWatson)
-
Aria-roledescription should not be a global attribute. w3c/aria#1132 (6 comments by @carmacleod, @jnurthen, @LaurenceRLewis, @stes-acc)
-
aria-disabled non-focusable descendents w3c/aria#1130 (5 comments by @aleventhal, @carmacleod, @jnurthen, @scottaohara, @stes-acc)
-
The aria-rowindex attribute being permitted on cells seems like a footgun w3c/aria#1138 (3 comments by @bathos, @JAWS-test)
-
Unclear purpose of `aria-valuemin` and `aria-valuemax` when `aria-valuetext` is used w3c/aria#1128 (2 comments by @JAWS-test, @joanmarie)
-
aria-roledescription should not duplicate the implicit or explicit role w3c/aria#1131 (2 comments by @JAWS-test, @pkra)
-
aria-roledescription should not be allowed on role generic w3c/aria#1140 (1 comment by @scottaohara)
-
Consider deprecating all special live region roles except alert w3c/aria#1104 (1 comment by @smhigley)
-
Update Managing Focus "Information for User Agents" section to include 1.2 combobox w3c/aria#1121 (1 comment by @mcking65)
-
-
10 pull requests opened in the SVG Accessibility Task Force.
-
prohibit aria-roledescription from role=generic w3c/aria#1142, by @scottaohara.
-
Add aria-description w3c/aria#1137, by @aleventhal.
-
Update aria-details w3c/aria#1136, by @aleventhal.
-
Add comment role w3c/aria#1135, by @aleventhal.
-
Add suggestion role w3c/aria#1134, by @aleventhal.
-
Add mark role w3c/aria#1133, by @aleventhal.
-
revise meter authoring advice w3c/aria#1129, by @scottaohara.
-
Clean up use of "may" w3c/aria#1127, by @zcorpan.
-
Remove outdated Related Concepts links w3c/aria#1125, by @smhigley.
-
fix two typos w3c/aria#1124, by @scottaohara.
-
-
7 pull requests in the SVG Accessibility Task Force received 43 new comments.
-
Clean up use of "may" w3c/aria#1127 (23 comments by @carmacleod, @jnurthen, @scottaohara, @tobie, @zcorpan)
-
prohibit aria-roledescription from role=generic w3c/aria#1142 (3 comments by @mtrootyy, @pkra, @scottaohara)
-
GitHub
w3c/svgwg
-
7 issues opened.
-
Change arc grammar to coordinates rather than numbers and flags. w3c/svgwg#755, by @tatarize.
-
consider more involved path shapes w3c/svgwg#754, by @ghost.
-
Rect decomposition is invalid w3c/svgwg#753, by @tatarize.
-
Subtleties of the path data grammar w3c/svgwg#752, by @dalboris.
-
Use shorter symbol names in SVG path data grammar w3c/svgwg#751, by @dalboris.
-
Third parameter of arc in path data should allow signed numbers w3c/svgwg#750, by @dalboris.
-
[animations] Remove the 'timelinebegin' attribute w3c/svgwg#749, by @fsoder.
-
-
1 issue reopened.
-
Subtleties of the path data grammar w3c/svgwg#752, by @dalboris.
-
-
14 issues received 53 new comments.
-
consider more involved path shapes w3c/svgwg#754 (11 comments by @BigBadaboom, @dalboris, @Doktorchen, @ghost)
-
Subtleties of the path data grammar w3c/svgwg#752 (6 comments by @BigBadaboom, @dalboris, @ghost, @tatarize)
-
Add support for the `hidden`-attribute w3c/svgwg#508 (5 comments by @AmeliaBR, @css-meeting-bot, @ZoeBijl)
-
Discard "discard" elements w3c/svgwg#717 (5 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @fsoder, @progers)
-
Need to better define what rules apply to an element in an <svg:use> subtree. w3c/svgwg#504 (3 comments by @dirkschulze, @fsoder, @george-steel)
-
Third parameter of arc in path data should allow signed numbers w3c/svgwg#750 (2 comments by @AmeliaBR, @dalboris)
-
SVG 2 spec section 13.5.7 (probably) incorrect for miter-clip (and arcs?) w3c/svgwg#745 (1 comment by @css-meeting-bot)
-
SVG2 spec means elements within a <use> tag can not be targeted for styling w3c/svgwg#367 (1 comment by @dirkschulze)
-
stacking context / rendering order requirements are mostly not Web compatible w3c/svgwg#463 (1 comment by @nikolaszimmermann)
-
[svg-native] [13. Gradients and Patterns] gradientUnits in SVG Native w3c/svgwg#746 (1 comment by @css-meeting-bot)
-
4 pull requests opened.
-
Make the .gitignore patterns more robust, and simpler w3c/svgwg#758, by @jwatt.
-
Remove old files from when we used Mercurial w3c/svgwg#757, by @jwatt.
-
Fix `make stabilize-issues-all-specs` w3c/svgwg#756, by @jwatt.
-
Rebase the SVG Native spec on top of SVG 2 w3c/svgwg#748, by @litherum.
-
-
3 pull requests merged.
-
Remove old files from when we used Mercurial w3c/svgwg#757.
-
Fix `make stabilize-issues-all-specs` w3c/svgwg#756.
-
Rebase the SVG Native spec on top of SVG 2 w3c/svgwg#748.
-
-
1 pull request received 13 new comments.
-
Rebase the SVG Native spec on top of SVG 2 w3c/svgwg#748 (13 comments by @AmeliaBR, @dirkschulze, @litherum)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
8 issues opened in the SVG Accessibility Task Force.
-
Should aria-haspopup allow tooltip as a supported token value? w3c/aria#1122, by @accdc.
-
Consider creation of a fieldsize/maxlength property w3c/aria#1119, by @joanmarie.
-
EDITORIAL: Clarify what it means to support "ARIA 1.0 combobox" w3c/aria#1118, by @zcorpan.
-
Consider prohibiting accessible name for listitem, rowgroup, term, time w3c/aria#1117, by @zcorpan.
-
AriaAttributes members need [CEReactions] w3c/aria#1116, by @annevk.
-
Revisit potentially outdated Related Concepts links w3c/aria#1114, by @smhigley.
-
-
29 issues closed in the SVG Accessibility Task Force.
-
[Role Parity] What do we do about details? w3c/aria#928.
-
[Role Parity] What do we do about object? w3c/aria#938.
-
[Role Parity] need role for fieldset w3c/aria#875.
-
rel attribute values w3c/aria#480.
-
target for anchors w3c/aria#481.
-
aria-readonly for button role w3c/aria#479.
-
HTML pre element w3c/aria#475.
-
@multiple w3c/aria#470.
-
ARIA: should there be a password role? w3c/aria#166.
-
New role for ruby? w3c/aria#74.
-
Role parity for html:code, html:var, html:samp, html:kbd w3c/aria#527.
-
Handle abbr w3c/aria#498.
-
HTML br and wbr w3c/aria#510.
-
Last Minute Pull Requests to Merge into stable w3c/aria#1092.
-
Need to check roles which support aria-expanded w3c/aria#681.
-
New ARIA role for a <meter> element? w3c/aria#451.
-
Should name be required on timer, log, table? w3c/aria#1005.
-
Consider prohibiting author naming certain roles w3c/aria#833.
-
input format property w3c/aria#466.
-
aria-controls a required property for Combobox? w3c/aria#776.
-
Does combobox require an accessible name? w3c/aria#1046.
-
1 issue reopened in the SVG Accessibility Task Force.
-
40 issues in the SVG Accessibility Task Force received 70 new comments.
-
Consider deprecating all special live region roles except alert w3c/aria#1104 (7 comments by @aardrian, @bolonio, @eps1lon, @scottaohara, @StommePoes)
-
Add some PR automation once we start 1.3 w3c/aria#1106 (7 comments by @carmacleod, @jnurthen, @joanmarie, @nschonni)
-
Should aria-haspopup allow tooltip as a supported token value? w3c/aria#1122 (5 comments by @accdc, @jnurthen, @scottaohara, @smhigley)
-
Is the text that prohibits changing roles obsolete? w3c/aria#986 (3 comments by @aleventhal, @mfairchild365)
-
What to do about aria-controls w3c/aria#995 (3 comments by @craigkovatch, @mcking65, @patrickhlauke)
-
ARIAMixin has many integer attributes with string types and uses DOMString? incorrectly w3c/aria#1110 (3 comments by @alice, @annevk)
-
Consider prohibiting accessible name for listitem, rowgroup, term, time w3c/aria#1117 (2 comments by @aleventhal, @scottaohara)
-
Is activating a tri-state toggle limited to toggling between aria-pressed=false and aria-pressed=true? w3c/aria#684 (2 comments by @jnurthen)
-
[Role Parity] What do we do about input (type=password)? w3c/aria#935 (2 comments by @annevk, @joanmarie)
-
w3c/aria#74 (1 comment by @joanmarie)
-
Add normative text to menuitem and treeitem about allowed child elements w3c/aria#1120 (1 comment by @jnurthen)
-
roledescription usage should not be limited to elements with defined ARIA roles w3c/aria#500 (1 comment by @jnurthen)
-
Update 'combobox' spec as per html spec/html-aam mapping for <select> element w3c/aria#817 (1 comment by @zcorpan)
-
role combobox either misses text or is incorrect regarding role searchbox w3c/aria#742 (1 comment by @zcorpan)
-
The ARIA 1.1 Combobox design pattern endorses unlabelled form fields as normative spec. w3c/aria#893 (1 comment by @zcorpan)
-
The Combobox 1.0 design pattern references incorrectly include aria-owns instead of aria-controls. w3c/aria#998 (1 comment by @zcorpan)
-
-
3 pull requests opened in the SVG Accessibility Task Force.
-
Remove URI from Value types w3c/aria#1115, by @carmacleod.
-
Remove remaining XForms references w3c/aria#1113, by @smhigley.
-
-
2 pull requests merged in the SVG Accessibility Task Force.
-
Fix combobox issues w3c/aria#1051.
-
2 pull requests in the SVG Accessibility Task Force received 9 new comments.
SVG Accessibility Task Force
GitHub
w3c/aria
-
25 issues opened in the SVG Accessibility Task Force.
-
"URI" attribute type is unused? w3c/aria#1111, by @domenic.
-
Place to collect feedback on ARIA Annotations proposal w3c/aria#1109, by @aleventhal.
-
Editorial: Remove parenthesis from headings w3c/aria#1108, by @LJWatson.
-
Why is aria-current=page limited to pagination links? w3c/aria#1107, by @JAWS-test.
-
Add some PR automation once we start 1.3 w3c/aria#1106, by @jnurthen.
-
Consider deprecating all special live region roles except alert w3c/aria#1104, by @mcking65.
-
fixing https://www.w3.org/WAI/ARIA/minutes w3c/aria#1103, by @pkra.
-
Guidance regarding aria-row/colindextext ordering? w3c/aria#1102, by @jcsteh.
-
Should aria-disabled be allowed on role=link? w3c/aria#1099, by @carmacleod.
-
Are all constraints inherited? w3c/aria#1096, by @jnurthen.
-
List of things specified in role definition is incomplete w3c/aria#1095, by @jnurthen.
-
aria-selected should be mandatory if no aria-activedescendant is used w3c/aria#1094, by @JAWS-test.
-
Last Minute Pull Requests to Merge into stable w3c/aria#1092, by @jnurthen.
-
Further global attribute considerations w3c/aria#1089, by @scottaohara.
-
consider a new role=icon w3c/aria#1088, by @DavidMacDonald.
-
Make the difference between menu and menubar clearer w3c/aria#1084, by @JAWS-test.
-
aria-activedescendant and focus events w3c/aria#1081, by @pkra.
-
Consider deprecating role=directory w3c/aria#1076, by @scottaohara.
-
Meter should not be in the list of widgets w3c/aria#1074, by @jnurthen.
-
-
37 issues closed in the SVG Accessibility Task Force.
-
Why is aria-current=page limited to pagination links? w3c/aria#1107.
-
Add additional details regarding the new caption role w3c/aria#901.
-
Meter should not be in the list of widgets w3c/aria#1074.
-
RDF model still useful? w3c/aria#672.
-
What are focusable elements with role=presentation? w3c/aria#1041.
-
Consider deprecating role=directory w3c/aria#1076.
-
Use of group within list is unclear w3c/aria#1011.
-
Remove normative should from tooltip role w3c/aria#1035.
-
discussion of aria-expanded on multi select tabpanels w3c/aria#1040.
-
Clarify combobox label placement w3c/aria#909.
-
Need cite role w3c/aria#873.
-
tabpanel - accessible name required conflicts with prose w3c/aria#965.
-
Create description (was:definition) list role w3c/aria#504.
-
Lists should also be able to take term definitions w3c/aria#503.
-
HTML definition list and definitions w3c/aria#477.
-
I think we need a definition of "User Interface Element" w3c/aria#815.
-
need role for sub and sup w3c/aria#877.
-
WAI-ARIA 1.1: aria-roledescription w3c/aria#83.
-
2 issues reopened in the SVG Accessibility Task Force.
-
Annotations w3c/aria#749, by @aleventhal.
-
Is the text that prohibits changing roles obsolete? w3c/aria#986, by @joanmarie.
-
-
49 issues in the SVG Accessibility Task Force received 127 new comments.
-
Clarify usage of aria-haspopup w3c/aria#1024 (18 comments by @carmacleod, @jnurthen, @joanmarie, @mfairchild365, @scottaohara)
-
Is the text that prohibits changing roles obsolete? w3c/aria#986 (9 comments by @aleventhal, @cookiecrook, @JAWS-test, @jcsteh, @joanmarie)
-
Write editorial note for each of the four no-longer-global properties for wide review spec w3c/aria#1105 (8 comments by @jnurthen, @joanmarie, @michael-n-cooper)
-
aria-activedescendant and focus events w3c/aria#1081 (7 comments by @JAWS-test, @jnurthen, @mcking65, @pkra)
-
Inserting content into live region vs turning on visibility w3c/aria#546 (6 comments by @JAWS-test, @jnurthen)
-
Editorial: Remove parenthesis from headings w3c/aria#1108 (5 comments by @jnurthen, @LJWatson, @pkra)
-
Revising what ARIA attributes should be considered global w3c/aria#999 (4 comments by @carmacleod, @jnurthen, @scottaohara)
-
consider a new role=icon w3c/aria#1088 (4 comments by @AmeliaBR, @carmacleod, @jnurthen, @scottaohara)
-
Why is aria-current=page limited to pagination links? w3c/aria#1107 (3 comments by @eps1lon, @LJWatson, @scottaohara)
-
Consider deprecating all special live region roles except alert w3c/aria#1104 (3 comments by @accdc, @JAWS-test, @mcking65)
-
Guidance regarding aria-row/colindextext ordering? w3c/aria#1102 (3 comments by @jcsteh, @joanmarie)
-
Make the difference between menu and menubar clearer w3c/aria#1084 (3 comments by @JAWS-test, @scottaohara, @smhigley)
-
Remove the string reflection properties that will be replaced by incompatible element reflection properties w3c/aria#834 (3 comments by @jnurthen, @joanmarie)
-
Add aria-posinset and aria-setsize to definition and term roles w3c/aria#497 (2 comments by @jnurthen, @scottaohara)
-
Something confuses me about TABS and aria-expanded / aria-selected w3c/aria#1091 (2 comments by @JAWS-test, @LaurenceRLewis)
-
Should extension specs be allowed to override required owned elements with subclasses? w3c/aria#1056 (2 comments by @pkra, @rdeltour)
-
Implicit values for required properties section needs revising w3c/aria#966 (2 comments by @jnurthen, @scottaohara)
-
I think we need a definition of "User Interface Element" w3c/aria#815 (2 comments by @jnurthen, @scottaohara)
-
ARIAMixin has many integer attributes with string types and uses DOMString? incorrectly w3c/aria#1110 (1 comment by @domenic)
-
Role Parity for semantically meaningless stylistic elements in HTML w3c/aria#485 (1 comment by @scottaohara)
-
Add handling author errors update for unnamed region and form landmarks? w3c/aria#1083 (1 comment by @JAWS-test)
-
Revisit normative ref to ui events keyboardevent key values when it hits rec w3c/aria#738 (1 comment by @jnurthen)
-
Is the attribute aria-level on role=grid and role=tablist necessary? w3c/aria#915 (1 comment by @scottaohara)
-
-
13 pull requests opened in the SVG Accessibility Task Force.
-
clarify “rendering” of aria-errormessage w3c/aria#1098, by @scottaohara.
-
brailleroledescription update w3c/aria#1097, by @pkra.
-
clarify use of alertdialog over alert roles w3c/aria#1090, by @scottaohara.
-
update introduction sentence to option role w3c/aria#1087, by @scottaohara.
-
update caption role for 1.2 w3c/aria#1086, by @scottaohara.
-
Fixing issue 546 w3c/aria#1082, by @JAWS-test.
-
deprecate role=directory w3c/aria#1080, by @scottaohara.
-
remove aria-level from tablist w3c/aria#1079, by @scottaohara.
-
WIP: revising required properties section - issue 966 w3c/aria#1078, by @scottaohara.
-
remove stray /a> after HTML link w3c/aria#1077, by @scottaohara.
-
Editorial: remove maxTocLevel for ReSpec config w3c/aria#1073, by @marcoscaceres.
-
24 pull requests merged in the SVG Accessibility Task Force.
-
update caption role for 1.2 w3c/aria#1086.
-
remove 4 Global States and properties (#999) w3c/aria#1023.
-
update introduction sentence to option role w3c/aria#1087.
-
clarify use of alertdialog over alert roles w3c/aria#1090.
-
remove aria-level from tablist w3c/aria#1079.
-
remove reference to taxonomy File w3c/aria#1070.
-
clarify “rendering” of aria-errormessage w3c/aria#1098.
-
feat: aria-brailleroledescription w3c/aria#924.
-
deprecate role=directory w3c/aria#1080.
-
Make Form Accessible Name Required True w3c/aria#1071.
-
remove allowance of group in lists w3c/aria#1053.
-
remove should from tooltip w3c/aria#1037.
-
Editorial: Add landmark language to definitions w3c/aria#1060.
-
Add implicit values for progressbar w3c/aria#1066.
-
Add note to fallback table w3c/aria#1067.
-
Fixing issue 546 w3c/aria#1082.
-
remove accessible name required from log and timer w3c/aria#1065.
-
Correct text to require aria-expanded on the tab w3c/aria#1059.
-
remove stray /a> after HTML link w3c/aria#1077.
-
space delimited -> space-separated w3c/aria#1064.
-
Add directory Required Context role to listitem w3c/aria#1062.
-
Remove roledescription examples w3c/aria#1061.
-
-
3 pull requests closed in the SVG Accessibility Task Force.
-
WIP: revising required properties section - issue 966 w3c/aria#1078.
-
Editorial: remove maxTocLevel for ReSpec config w3c/aria#1073.
-
28 pull requests in the SVG Accessibility Task Force received 197 new comments.
-
remove 4 Global States and properties (#999) w3c/aria#1023 (28 comments by @accdc, @carmacleod, @jnurthen, @LJWatson, @scottaohara, @smhigley, @stes-acc)
-
Issue1019 initial draft for accessible name using caption role w3c/aria#1020 (23 comments by @jongund, @scottaohara)
-
remove reference to taxonomy File w3c/aria#1070 (13 comments by @jnurthen, @marcoscaceres, @mcking65)
-
brailleroledescription update w3c/aria#1097 (12 comments by @cookiecrook, @joanmarie, @mcking65, @pkra)
-
update caption role for 1.2 w3c/aria#1086 (11 comments by @jnurthen, @joanmarie, @mcking65, @scottaohara)
-
ARIA: Editorial cleanup needed to "Presentational Roles Conflict Reso… w3c/aria#852 (11 comments by @carmacleod, @joanmarie, @scottaohara)
-
Make Form Accessible Name Required True w3c/aria#1071 (10 comments by @jnurthen, @joanmarie, @jongund, @mcking65, @scottaohara)
-
clarify use of alertdialog over alert roles w3c/aria#1090 (8 comments by @carmacleod, @jnurthen, @mcking65, @scottaohara)
-
Clarify wording in "Including Elements in the Accessibility Tree" section w3c/aria#1100 (7 comments by @carmacleod, @jnurthen, @mcking65)
-
removes the old default aria-checked value from properties table w3c/aria#1069 (7 comments by @jnurthen, @joanmarie, @mcking65, @scottaohara)
-
Tree Inclusion focus/activedescendant requirements need clarification… w3c/aria#950 (5 comments by @carmacleod)
-
[WIP] Merge remaining changes from #813 into stable w3c/aria#828 (5 comments by @jnurthen, @joanmarie, @kbunge63)
-
Option role: Change aria-selected from required to supported and remove default value w3c/aria#799 (3 comments by @JAWS-test, @mcking65, @melanierichards)
-
Add directory Required Context role to listitem w3c/aria#1062 (3 comments by @joanmarie, @scottaohara)
-
remove accessible name required from log and timer w3c/aria#1065 (2 comments by @jnurthen, @jongund)
-
Initial aria-textseparation (depends on generic PR being merged) w3c/aria#996 (1 comment by @carmacleod)
-
Merge once Meter hits stable: Move Meter from widget list to structure list w3c/aria#1075 (1 comment by @jnurthen)
-
Participants
-
1 organization joined.
-
Igalia joined.
-
GitHub
w3c/svgwg
-
4 issues opened.
-
[svg-native] [13. Gradients and Patterns] gradientUnits in SVG Native w3c/svgwg#746, by @zauguin.
-
SVG 2 spec section 13.5.7 (probably) incorrect for miter-clip (and arcs?) w3c/svgwg#745, by @skef.
-
Clarify behavior of pointer-events on nested elements w3c/svgwg#744, by @yi-gu.
-
10 issues received 39 new comments.
-
SVG 2 spec section 13.5.7 (probably) incorrect for miter-clip (and arcs?) w3c/svgwg#745 (10 comments by @AmeliaBR, @css-meeting-bot, @skef, @Tavmjong)
-
Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents w3c/svgwg#706 (8 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @progers, @saschanaz, @shallawa, @smfr)
-
[svg-native] [13. Gradients and Patterns] gradientUnits in SVG Native w3c/svgwg#746 (6 comments by @AmeliaBR, @dirkschulze, @msand, @zauguin)
-
Need to better define what rules apply to an element in an <svg:use> subtree. w3c/svgwg#504 (4 comments by @emilio, @george-steel)
-
Revert changes for removing SVGViewSpec interface and SVGSVGElement.currentView w3c/svgwg#747 (2 comments by @AmeliaBR, @longsonr)
-
SVG2 spec means elements within a <use> tag can not be targeted for styling w3c/svgwg#367 (2 comments by @theprojectsomething, @ThomasBrierley)
-
Clarify behavior of pointer-events on nested elements w3c/svgwg#744 (2 comments by @AmeliaBR, @fsoder)
-
-
1 pull request opened.
-
Delete Makefile w3c/svgwg#743, by @bernadeth10.
-
-
1 pull request closed.
-
Delete Makefile w3c/svgwg#743.
-
-
1 pull request received 4 new comments.
SVG Accessibility Task Force
GitHub
w3c/aria
-
10 issues opened in the SVG Accessibility Task Force.
-
Which ARIA attributes apply to descendant elements? w3c/aria#1063, by @JAWS-test.
-
AriaAttributes cannot be nullable w3c/aria#1058, by @annevk.
-
What is the value of textbox or searchbox? w3c/aria#1057, by @JAWS-test.
-
hidden and css visibility w3c/aria#1055, by @eps1lon.
-
Output of child elements w3c/aria#1054, by @JAWS-test.
-
aria-checked on option and treeitem w3c/aria#1052, by @smhigley.
-
heading with aria-level > 6 w3c/aria#1050, by @JAWS-test.
-
Let web developers signal their "DPAD mechanics" w3c/aria#1049, by @hugoholgersson.
-
Description at aria-relevant incomprehensible and wrong w3c/aria#1048, by @JAWS-test.
-
-
51 issues closed in the SVG Accessibility Task Force.
-
Is the use of the word "node" correct in aria-atomic w3c/aria#709.
-
Let web developers signal their "DPAD mechanics" w3c/aria#1049.
-
Tokens for aria-autocomplete w3c/aria#1047.
-
reword or remove excess notes in #aria-hidden w3c/aria#726.
-
ARIA 1.1 inconsistent progressbar superclass w3c/aria#686.
-
Confusing sentence in presentation role discussion w3c/aria#717.
-
Unclear sentence in editor's note in scrollbar role w3c/aria#914.
-
Why is toolbar as a document structure role? w3c/aria#713.
-
Boolean attribute oddity with relation to HTML5 w3c/aria#703.
-
Clarify aria-hidden wording w3c/aria#705.
-
Work on getting AT to follow pronunciation hints w3c/aria#752.
-
role:nameFrom needs "unsupported" value w3c/aria#720.
-
Browser support for element/attribute reflection? w3c/aria#957.
-
aria-valuenow implicit value is always 50 for separator w3c/aria#959.
-
Fix association of definition and term roles w3c/aria#970.
-
Please clarify group role w3c/aria#786.
-
Required properties and default values w3c/aria#787.
-
spinbutton required and supported properties w3c/aria#861.
-
Definition description and aria-labelledby w3c/aria#836.
-
Output of child elements w3c/aria#1054.
-
“Todo” notice still in rec document w3c/aria#863.
-
article role does not support aria-level w3c/aria#669.
-
Clarify use of aria-label on elements with no role w3c/aria#756.
-
Issues with role: checkbox w3c/aria#579.
-
aside vs role=note w3c/aria#918.
-
aria-controls should only point to visible elements w3c/aria#531.
-
Tooltip role should allow referencing by aria-labelledby w3c/aria#987.
-
Inconsistent text for role=spinbutton w3c/aria#642.
-
Figure out what the heck to do with the <time> element w3c/aria#507.
-
HTML optgroup element w3c/aria#473.
-
What is the value of textbox or searchbox? w3c/aria#1057.
-
Agenda for TPAC 2019 w3c/aria#1001.
-
Specification for live region not clear enough w3c/aria#1043.
-
Should aria-invalid be a token list? w3c/aria#1045.
-
-
90 issues in the SVG Accessibility Task Force received 185 new comments.
-
aria-checked on option and treeitem w3c/aria#1052 (14 comments by @accdc, @JAWS-test, @LJWatson, @mcking65, @scottaohara, @smhigley)
-
Agenda for TPAC 2019 w3c/aria#1001 (12 comments by @annevk, @cookiecrook, @css-meeting-bot, @jnurthen, @joanmarie, @jugglinmike, @zcorpan)
-
aria-valuetext would be useful on many more roles w3c/aria#711 (8 comments by @JAWS-test, @stevefaulkner, @ZoeBijl)
-
Inserting content into live region vs turning on visibility w3c/aria#546 (7 comments by @JAWS-test, @jnurthen)
-
Allowing `aria-hidden` on visible content excludes low vision uses w3c/aria#583 (7 comments by @eps1lon, @jnurthen, @ZoeBijl)
-
[Role Parity] What do we do about input (type=password)? w3c/aria#935 (6 comments by @jnurthen, @johnfoliot)
-
Clarify how live region content be announced, given shadow DOM? w3c/aria#1017 (6 comments by @annevk, @domenic, @jnurthen, @scottaohara, @zcorpan)
-
Clarify what browsers should do with text replaced with same text in a live region w3c/aria#671 (5 comments by @JAWS-test, @jnurthen)
-
Let web developers signal their "DPAD mechanics" w3c/aria#1049 (5 comments by @hugoholgersson, @jnurthen, @pkra)
-
Description at aria-relevant incomprehensible and wrong w3c/aria#1048 (4 comments by @JAWS-test, @jnurthen)
-
`aria-details` precedence over `aria-describedby` w3c/aria#1009 (4 comments by @cookiecrook, @jnurthen)
-
Should extension specs be allowed to override required owned elements with subclasses? w3c/aria#1056 (4 comments by @jnurthen, @joanmarie)
-
Is the use of the word "node" correct in aria-atomic w3c/aria#709 (3 comments by @JAWS-test, @jnurthen)
-
aria-atomic doesn't say what its missing/invalid value defaults are w3c/aria#976 (3 comments by @jnurthen)
-
Should aria-selected be allowed on row, columnheader, or rowheader in table? w3c/aria#1008 (3 comments by @jnurthen, @joanmarie, @zcorpan)
-
Develop a list of accessibility evaluation rules based on the aria spec and aria authoring practices w3c/aria#670 (2 comments by @jnurthen, @jongund)
-
Slider: Specify a decimal value for valuenow, valuemin, valuemax w3c/aria#706 (2 comments by @jnurthen)
-
Consider addition of property(ies) to expose braille string w3c/aria#765 (2 comments by @joanmarie, @pkra)
-
Need 'aria-selected' and 'aria-controls' as 'Required States and Properties' when using role 'tab' w3c/aria#690 (1 comment by @jnurthen)
-
`aria-sort` forces `role="columnheader"` or `rowheader` Validation throws error on `<th>` w3c/aria#592 (1 comment by @jnurthen)
-
Consider adding context attribute through which ATs could ensure correct presentation of content w3c/aria#767 (1 comment by @jnurthen)
-
Clarify that aria-multiline should not be changed on the fly because it impacts role mapping w3c/aria#727 (1 comment by @jnurthen)
-
Clean up instances of "space-delimited", "space delimited", and "space-separated." w3c/aria#728 (1 comment by @jnurthen)
-
The WAI-ARIA Role, State, and Property Quick Reference is still a placeholder w3c/aria#409 (1 comment by @jnurthen)
-
[Role Parity] What do we do about input (type=datetime-local)? w3c/aria#932 (1 comment by @jnurthen)
-
w3c/aria#74 (1 comment by @jnurthen)
-
Why role=presentation is ignored due to a global ARIA property? w3c/aria#1042 (1 comment by @scottaohara)
-
Update required owned element for role 'combobox' and required context role for role 'option' w3c/aria#818 (1 comment by @jnurthen)
-
Consider prohibiting name from contents for rows in static (non-grid) tables w3c/aria#1022 (1 comment by @joanmarie)
-
w3c/aria#79 (1 comment by @joanmarie)
-
Support an attribute like aria-posindom that lets us modify a11y tree without modifying DOM order w3c/aria#1021 (1 comment by @carmacleod)
-
Each ARIA role entry characteristics table should have a "can have focusable descendants" entry w3c/aria#1028 (1 comment by @JAWS-test)
-
`listitem` role seems to be missing `directory` as required context role w3c/aria#1030 (1 comment by @jnurthen)
-
aria-relevant: find real-world use cases, consider deprecating it w3c/aria#712 (1 comment by @JAWS-test)
-
-
15 pull requests opened in the SVG Accessibility Task Force.
-
Aria-relevant clarifications for #1048 w3c/aria#1072, by @jnurthen.
-
Make Form Accessible Name Required True w3c/aria#1071, by @jnurthen.
-
remove reference to taxonomy File w3c/aria#1070, by @jnurthen.
-
removes the old default aria-checked value from properties table w3c/aria#1069, by @scottaohara.
-
remove sentence from note in scrollbar role w3c/aria#1068, by @scottaohara.
-
Add note to fallback table w3c/aria#1067, by @jnurthen.
-
Add implicit values for progressbar w3c/aria#1066, by @jnurthen.
-
remove accessible name required from log and timer w3c/aria#1065, by @jnurthen.
-
space delimited -> space-separated w3c/aria#1064, by @jnurthen.
-
Add directory Required Context role to listitem w3c/aria#1062, by @jnurthen.
-
Remove roledescription examples w3c/aria#1061, by @jnurthen.
-
Editorial: Add landmark language to definitions w3c/aria#1060, by @jnurthen.
-
Correct text to require aria-expanded on the tab w3c/aria#1059, by @jnurthen.
-
remove allowance of group in lists w3c/aria#1053, by @scottaohara.
-
Fix combobox issues w3c/aria#1051, by @mcking65.
-
-
1 pull request merged in the SVG Accessibility Task Force.
-
remove sentence from note in scrollbar role w3c/aria#1068.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
10 pull requests in the SVG Accessibility Task Force received 36 new comments.
-
Editorial: Add landmark language to definitions w3c/aria#1060 (4 comments by @carmacleod, @jnurthen)
-
removes the old default aria-checked value from properties table w3c/aria#1069 (3 comments by @jnurthen, @scottaohara)
-
Issue1019 initial draft for accessible name using caption role w3c/aria#1020 (3 comments by @carmacleod, @jongund)
-
Move Aria Orientation on scrollbar to supported section (from required) w3c/aria#781 (1 comment by @jnurthen)
-
Option role: Change aria-selected from required to supported and remove default value w3c/aria#799 (1 comment by @jnurthen)
GitHub
w3c/svgwg
-
7 issues opened.
-
window event attribute category is not referenced w3c/svgwg#741, by @heycam.
-
Baseline information for contextual layout w3c/svgwg#739, by @litherum.
-
Why does xmlns use http not https? w3c/svgwg#738, by @nothingismagick.
-
SVG 2.0 path number production only allows integers w3c/svgwg#737, by @dd8.
-
Compatibility of focusability with HTML & platform conventions w3c/svgwg#736, by @AmeliaBR.
-
Trying to understand the 'enable-background' property w3c/svgwg#733, by @RazrFalcon.
-
SVGWG Agenda TPAC 2019 w3c/svgwg#731, by @dirkschulze.
-
-
8 issues closed.
-
Event handler attributes language is not very clear w3c/svgwg#719.
-
Defer onfocusin and onfocusout w3c/svgwg#715.
-
Why does xmlns use http not https? w3c/svgwg#738.
-
SVG no longer defines any attributes as required w3c/svgwg#710.
-
Typo `referrerpolicy` content attribute type definition w3c/svgwg#712.
-
SVG 2.0 path number production only allows integers w3c/svgwg#737.
-
Update spec to new IDL syntax for optional dictionaries w3c/svgwg#727.
-
Trying to understand the 'enable-background' property w3c/svgwg#733.
-
-
19 issues received 57 new comments.
-
Baseline information for contextual layout w3c/svgwg#739 (9 comments by @faceless2, @heycam, @litherum)
-
window event attribute category is not referenced w3c/svgwg#741 (8 comments by @AmeliaBR, @dirkschulze, @heycam)
-
SVGWG Agenda TPAC 2019 w3c/svgwg#731 (8 comments by @AmeliaBR, @aphillips, @css-meeting-bot, @dirkschulze, @foolip, @gsnedders, @litherum)
-
SVG2 spec means elements within a <use> tag can not be targeted for styling w3c/svgwg#367 (7 comments by @bureau-of-information, @css-meeting-bot, @dirkschulze)
-
SVG no longer defines any attributes as required w3c/svgwg#710 (4 comments by @AmeliaBR, @dirkschulze, @ewilligers)
-
Why does xmlns use http not https? w3c/svgwg#738 (4 comments by @dirkschulze, @heycam, @nothingismagick)
-
Compatibility of focusability with HTML & platform conventions w3c/svgwg#736 (2 comments by @AmeliaBR, @css-meeting-bot)
-
Referencing SVGs through USE from other domains w3c/svgwg#707 (2 comments by @css-meeting-bot, @Malvoz)
-
Update spec to new IDL syntax for optional dictionaries w3c/svgwg#727 (2 comments by @ewilligers, @Ms2ger)
-
Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. w3c/svgwg#537 (1 comment by @css-meeting-bot)
-
Text with multiple x="" values should be shaped as if it was not broken w3c/svgwg#631 (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 @emilio)
-
xlink:href in <animate>, <use>, etc. doesn't work in sourceless iframes w3c/svgwg#700 (1 comment by @css-meeting-bot)
-
-
5 pull requests opened.
-
tweak styling of the header links w3c/svgwg#742, by @heycam.
-
Remove onfocusin and onfocusout event attributes. w3c/svgwg#740, by @heycam.
-
Fix case of referrerpolicy="" attribute. w3c/svgwg#735, by @heycam.
-
Default value '{}' is specified for optional dict w3c/svgwg#732, by @ewilligers.
-
-
7 pull requests merged.
-
tweak styling of the header links w3c/svgwg#742.
-
Remove onfocusin and onfocusout event attributes. w3c/svgwg#740.
-
Link to definition of color for stop-color syntax w3c/svgwg#729.
-
Fix case of referrerpolicy="" attribute. w3c/svgwg#735.
-
Fix typos w3c/svgwg#734.
-
Default value '{}' is specified for optional dict w3c/svgwg#732.
-
Fixed missing word, and changed one w3c/svgwg#730.
-
-
1 pull request closed.
-
Fixed path grammar w3c/svgwg#346.
-
-
5 pull requests received 10 new comments.
-
Remove onfocusin and onfocusout event attributes. w3c/svgwg#740 (3 comments by @dirkschulze, @heycam)
-
Link to definition of color for stop-color syntax w3c/svgwg#729 (3 comments by @dirkschulze, @ewilligers)
-
w3c/svg-aam
-
1 issue opened.
-
SVG with ARIA roles w3c/svg-aam#11, by @JAWS-test.
-
GitHub
w3c/svgwg
-
8 issues opened.
-
Update spec to new IDL syntax for optional dictionaries w3c/svgwg#727, by @Ms2ger.
-
'autofocus' attribute support w3c/svgwg#726, by @tkent-google.
-
vector-effect grammar should allow multiple effects w3c/svgwg#725, by @AmeliaBR.
-
Improve SMIL "Parsing timing specifiers" instructions w3c/svgwg#722, by @ospencer.
-
Question about <use> inside a <clipPath> w3c/svgwg#720, by @RazrFalcon.
-
Event handler attributes language is not very clear w3c/svgwg#719, by @bzbarsky.
-
-
5 issues closed.
-
'autofocus' attribute support w3c/svgwg#726.
-
Decide what to do with zoom and pan w3c/svgwg#56.
-
Question about <use> inside a <clipPath> w3c/svgwg#720.
-
-
11 issues received 31 new comments.
-
What properties from a style element or attribute should be applied to an element? w3c/svgwg#721 (7 comments by @BigBadaboom, @RazrFalcon, @tabatkins)
-
'autofocus' attribute support w3c/svgwg#726 (6 comments by @AmeliaBR, @css-meeting-bot, @domenic, @longsonr, @tkent-google)
-
How to handle feColorMatrix with type=saturate and values outside a 0..1 range? w3c/svgwg#723 (4 comments by @AmeliaBR, @dirkschulze, @RazrFalcon)
-
Referencing SVGs through USE from other domains w3c/svgwg#707 (3 comments by @AmeliaBR, @longsonr, @waterplea)
-
Question about <use> inside a <clipPath> w3c/svgwg#720 (3 comments by @AmeliaBR, @BigBadaboom, @RazrFalcon)
-
vector-effect grammar should allow multiple effects w3c/svgwg#725 (2 comments by @css-meeting-bot, @satakagi)
-
Need to better define what rules apply to an element in an <svg:use> subtree. w3c/svgwg#504 (1 comment by @SebastianZ)
-
[svg-native] Decide whether reusable graphical elements are needed w3c/svgwg#689 (1 comment by @litherum)
-
-
4 pull requests opened.
-
Fixed missing word, and changed one w3c/svgwg#730, by @BigBadaboom.
-
Link to definition of color for stop-color syntax w3c/svgwg#729, by @ewilligers.
-
Add 'autofocus' core attribute w3c/svgwg#728, by @tkent-google.
-
Remove zoomAndPan attribute w3c/svgwg#724, by @AmeliaBR.
-
-
2 pull requests merged.
-
Add 'autofocus' core attribute w3c/svgwg#728.
-
Remove zoomAndPan attribute w3c/svgwg#724.
-
-
3 pull requests received 7 new comments.
-
Link to definition of color for stop-color syntax w3c/svgwg#729 (2 comments by @AmeliaBR, @ewilligers)
SVG Accessibility Task Force
GitHub
w3c/aria
-
19 issues opened in the SVG Accessibility Task Force.
-
Tokens for aria-autocomplete w3c/aria#1047, by @johnfoliot.
-
Does combobox require an accessible name? w3c/aria#1046, by @WilcoFiers.
-
Should aria-invalid be a token list? w3c/aria#1045, by @joanmarie.
-
Create property for repeated content w3c/aria#1044, by @joanmarie.
-
Specification for live region not clear enough w3c/aria#1043, by @JAWS-test.
-
Why role=presentation is ignored due to a global ARIA property? w3c/aria#1042, by @JAWS-test.
-
What are focusable elements with role=presentation? w3c/aria#1041, by @JAWS-test.
-
discussion of aria-expanded on multi select tabpanels w3c/aria#1040, by @DavidMacDonald.
-
Consider making the accessible name optional for the table role w3c/aria#1039, by @mfairchild365.
-
Requesting new feature for label synonyms w3c/aria#1038, by @cookiecrook.
-
Remove normative should from tooltip role w3c/aria#1035, by @jnurthen.
-
Implicit role=presentation except for Required Owned Elements w3c/aria#1034, by @JAWS-test.
-
Clarify "required owned element" w3c/aria#1033, by @WilcoFiers.
-
Issues with aria-expanded on tabpanel/tablist/tab w3c/aria#1032, by @zcorpan.
-
Should feed be a subclass of list? w3c/aria#1031, by @jnurthen.
-
Revisit allowed roles for aria-expanded w3c/aria#1026, by @smhigley.
-
Clarify usage of aria-haspopup w3c/aria#1024, by @scottaohara.
-
-
5 issues closed in the SVG Accessibility Task Force.
-
Consider removing aria-level from grid w3c/aria#743.
-
local files not generated into editor's drafts w3c/aria#955.
-
-
1 issue reopened in the SVG Accessibility Task Force.
-
Requesting new feature for label synonyms w3c/aria#1038, by @jnurthen.
-
-
32 issues in the SVG Accessibility Task Force received 83 new comments.
-
`listitem` role seems to be missing `directory` as required context role w3c/aria#1030 (7 comments by @annethyme, @LaurenceRLewis, @mcking65, @pkra, @WilcoFiers)
-
Support an attribute like aria-posindom that lets us modify a11y tree without modifying DOM order w3c/aria#1021 (6 comments by @aleventhal, @joanmarie, @LJWatson)
-
Does combobox require an accessible name? w3c/aria#1046 (4 comments by @accdc, @aleventhal, @jnurthen)
-
Each ARIA role entry characteristics table should have a "can have focusable descendants" entry w3c/aria#1028 (4 comments by @accdc, @jnurthen, @Wildebrew)
-
Is the attribute aria-level on role=grid and role=tablist necessary? w3c/aria#915 (4 comments by @a11ydoer, @curtbellew, @jnurthen, @smhigley)
-
Definition of "owned" is not strict enough; should actually be direct children, not any descendant w3c/aria#748 (3 comments by @joanmarie, @mattgarrish, @rdeltour)
-
discussion of aria-expanded on multi select tabpanels w3c/aria#1040 (3 comments by @accdc, @jnurthen)
-
Consider making the accessible name optional for the table role w3c/aria#1039 (3 comments by @johnfoliot, @mfairchild365)
-
aria-relevant: find real-world use cases, consider deprecating it w3c/aria#712 (2 comments by @JAWS-test)
-
Implicit role=presentation except for Required Owned Elements w3c/aria#1034 (2 comments by @JAWS-test, @mcking65)
-
The Combobox 1.0 design pattern references incorrectly include aria-owns instead of aria-controls. w3c/aria#998 (2 comments by @mcking65, @melanierichards)
-
Should aria-selected be allowed on row, columnheader, or rowheader in table? w3c/aria#1008 (2 comments by @mcking65)
-
Revising what ARIA attributes should be considered global w3c/aria#999 (2 comments by @carmacleod, @scottaohara)
-
The ARIA 1.1 Combobox design pattern endorses unlabelled form fields as normative spec. w3c/aria#893 (1 comment by @jnurthen)
-
Why can not the author use aria-labelledby if the interface can not display the label on the screen? w3c/aria#1007 (1 comment by @jnurthen)
-
w3c/aria#79 (1 comment by @mcking65)
-
Consider prohibiting name from contents for rows in static (non-grid) tables w3c/aria#1022 (1 comment by @mcking65)
-
5 pull requests opened in the SVG Accessibility Task Force.
-
remove should from tooltip w3c/aria#1037, by @jnurthen.
-
Remove should from tooltip role definition w3c/aria#1036, by @jnurthen.
-
fix(grid): removes aria-level from grid w3c/aria#1029, by @schne324.
-
Add img elements in gh-pages directory w3c/aria#1027, by @Rondinelly.
-
Editorial: fixes minor typos and spelling errors w3c/aria#1025, by @carmacleod.
-
-
2 pull requests merged in the SVG Accessibility Task Force.
-
fix(grid): removes aria-level from grid w3c/aria#1029.
-
Add img elements in gh-pages directory w3c/aria#1027.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
Remove should from tooltip role definition w3c/aria#1036.
-
-
7 pull requests in the SVG Accessibility Task Force received 23 new comments.
-
Editorial: fixes minor typos and spelling errors w3c/aria#1025 (6 comments by @carmacleod, @jnurthen, @schne324)
-
Issue1019 initial draft for accessible name using caption role w3c/aria#1020 (3 comments by @jongund, @scottaohara)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
11 issues opened in the SVG Accessibility Task Force.
-
Accessible name from caption w3c/aria#1019, by @jongund.
-
Clarify how live region content be announced, given shadow DOM? w3c/aria#1017, by @domenic.
-
Abstract role "Note" inconsistencies w3c/aria#1015, by @carmacleod.
-
If "Name From: prohibited", remove "Accessible Name Required: False" w3c/aria#1014, by @carmacleod.
-
Text Logos as links w3c/aria#1013, by @7dITS.
-
Question: Is there a role type for social media share button groups w3c/aria#1012, by @ghost.
-
Use of group within list is unclear w3c/aria#1011, by @JAWS-test.
-
Phonetic cues? w3c/aria#1010, by @jcayzac.
-
`aria-details` precedence over `aria-describedby` w3c/aria#1009, by @jongund.
-
9 issues closed in the SVG Accessibility Task Force.
-
remove references to XForms w3c/aria#983.
-
Text Logos as links w3c/aria#1013.
-
The Roles model introduces a potential timing problem w3c/aria#729.
-
Gridcell has accessible name required w3c/aria#993.
-
Phonetic cues? w3c/aria#1010.
-
Prep for October ARIA 1.2 (aka "1.2.2") Working Draft w3c/aria#827.
-
-
1 issue reopened in the SVG Accessibility Task Force.
-
What to do about aria-controls w3c/aria#995, by @mcking65.
-
-
15 issues in the SVG Accessibility Task Force received 34 new comments.
-
Question: Is there a role type for social media share button groups w3c/aria#1012 (7 comments by @AmeliaBR, @ghost, @LJWatson, @mcking65)
-
What to do about aria-controls w3c/aria#995 (6 comments by @barlowm, @DavidMacDonald, @LJWatson, @mcking65)
-
Is the attribute aria-level on role=grid and role=tablist necessary? w3c/aria#915 (2 comments by @a11ydoer, @jnurthen)
-
Consider prohibiting name from contents for rows in static (non-grid) tables w3c/aria#1022 (2 comments by @jcsteh, @joanmarie)
-
Should aria-selected be allowed on row, columnheader, or rowheader in table? w3c/aria#1008 (2 comments by @joanmarie)
-
Option role has confusing/contradictory/circular context roles specified w3c/aria#809 (1 comment by @kevinSuttle)
-
Support an attribute like aria-posindom that lets us modify a11y tree without modifying DOM order w3c/aria#1021 (1 comment by @carmacleod)
-
Remove base and related concepts rows from Characteristics tables w3c/aria#1003 (1 comment by @jnurthen)
-
-
4 pull requests opened in the SVG Accessibility Task Force.
-
remove 4 Global States and properties (#999) w3c/aria#1023, by @jnurthen.
-
Issue1019 initial draft for accessible name using caption role w3c/aria#1020, by @jongund.
-
Issue899 accname from heading w3c/aria#1018, by @jongund.
-
fixes #1014 w3c/aria#1016, by @carmacleod.
-
-
6 pull requests merged in the SVG Accessibility Task Force.
-
[editorial] removed obsolete references. Resolves #983 w3c/aria#997.
-
initial draft for role="generic" issue #699 w3c/aria#805.
-
fixes #1014 w3c/aria#1016.
-
Remove advice against changing roles w3c/aria#1006.
-
Name Not Required on gridcell w3c/aria#1004.
-
Issue504 description list roles w3c/aria#951.
-
-
3 pull requests in the SVG Accessibility Task Force received 19 new comments.
-
initial draft for role="generic" issue #699 w3c/aria#805 (9 comments by @carmacleod, @joanmarie, @jongund, @mcking65, @scottaohara)
-
GitHub
w3c/svgwg
-
10 issues opened.
-
Remove outdated note on hit-testing and root element w3c/svgwg#718, by @AmeliaBR.
-
Discard "discard" elements w3c/svgwg#717, by @FredTheDino.
-
Defer onfocusin and onfocusout w3c/svgwg#715, by @takenspc.
-
How should ResizeObserver work for SVG layout elements? w3c/svgwg#713, by @AmeliaBR.
-
Typo `referrerpolicy` content attribute type definition w3c/svgwg#712, by @takenspc.
-
text-overflow property is missing from attribute index w3c/svgwg#711, by @SebastianZ.
-
SVG no longer defines any attributes as required w3c/svgwg#710, by @sideshowbarker.
-
SVGAElement has a clashing definition of href w3c/svgwg#709, by @lukebjerring.
-
Referencing SVGs through USE from other domains w3c/svgwg#707, by @waterplea.
-
-
5 issues closed.
-
A separate MIME type for svgz files is needed w3c/svgwg#701.
-
text-overflow property is missing from attribute index w3c/svgwg#711.
-
SVGAElement has a clashing definition of href w3c/svgwg#709.
-
-
18 issues received 63 new comments.
-
Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents w3c/svgwg#706 (10 comments by @AmeliaBR, @css-meeting-bot, @longsonr, @saschanaz, @shallawa)
-
[svg-native] Decide whether reusable graphical elements are needed w3c/svgwg#689 (8 comments by @AmeliaBR, @behdad, @chris-little, @css-meeting-bot, @sairuspatel)
-
Referencing SVGs through USE from other domains w3c/svgwg#707 (7 comments by @AmeliaBR, @css-meeting-bot, @fsoder, @longsonr, @waterplea)
-
SVGAElement implements two conflicting interfaces w3c/svgwg#312 (6 comments by @AmeliaBR, @css-meeting-bot, @longsonr, @lukebjerring)
-
Discard "discard" elements w3c/svgwg#717 (5 comments by @birtles, @cconcolato, @dirkschulze, @progers)
-
text-overflow property is missing from attribute index w3c/svgwg#711 (5 comments by @AmeliaBR, @SebastianZ)
-
xlink:href in <animate>, <use>, etc. doesn't work in sourceless iframes w3c/svgwg#700 (3 comments by @AmeliaBR, @css-meeting-bot, @rniwa)
-
Typo `referrerpolicy` content attribute type definition w3c/svgwg#712 (2 comments by @dirkschulze, @longsonr)
-
Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript w3c/svgwg#291 (2 comments by @AmeliaBR, @css-meeting-bot)
-
Tracking issue for the renaming of HTMLOrSVGElement to something inclusive for MathML w3c/svgwg#708 (2 comments by @AmeliaBR, @ExE-Boss)
-
How should ResizeObserver work for SVG layout elements? w3c/svgwg#713 (1 comment by @css-meeting-bot)
-
[svg-native] Which CSS concepts should be supported in presentation attributes? w3c/svgwg#681 (1 comment by @css-meeting-bot)
-
-
2 pull requests opened.
-
Expanded note on server configuration and SVGZ w3c/svgwg#716, by @AmeliaBR.
-
-
2 pull requests merged.
-
Expanded note on server configuration and SVGZ w3c/svgwg#716.
-
-
1 pull request received 3 new comments.
-
Make "show" widget in element definitions boxes play nicely with screen readers w3c/svgwg#714 (3 comments by @AmeliaBR)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
12 issues opened in the SVG Accessibility Task Force.
-
Should name be required on timer, log, table? w3c/aria#1005, by @zcorpan.
-
Remove base and related concepts rows from Characteristics tables w3c/aria#1003, by @joanmarie.
-
Agenda for TPAC 2019 w3c/aria#1001, by @jnurthen.
-
Revising what ARIA attributes should be considered global w3c/aria#999, by @scottaohara.
-
What to do about aria-controls w3c/aria#995, by @scottaohara.
-
Gridcell has accessible name required w3c/aria#993, by @jnurthen.
-
propose an text based aria-description based on aria-label w3c/aria#992, by @DavidMacDonald.
-
ARIA Data Visualisation module w3c/aria#991, by @LJWatson.
-
9 issues closed in the SVG Accessibility Task Force.
-
Should rowgroup really support name from: contents? w3c/aria#896.
-
Suggest disallowing aria-disabled on role="link" w3c/aria#990.
-
role="row" needs to support aria-setsize, aria-posinset w3c/aria#558.
-
Scrollbar required and supported properties w3c/aria#858.
-
slider required and supported properties w3c/aria#860.
-
separator required and supported properties w3c/aria#859.
-
-
25 issues in the SVG Accessibility Task Force received 77 new comments.
-
Consider a "token" role for next version w3c/aria#689 (11 comments by @AmeliaBR, @carmacleod, @cookiecrook, @DavidMacDonald, @jnurthen, @stes-acc)
-
Remove base and related concepts rows from Characteristics tables w3c/aria#1003 (10 comments by @carmacleod, @jnurthen, @joanmarie)
-
What to do about aria-controls w3c/aria#995 (7 comments by @carmacleod, @joanmarie, @LJWatson, @scottaohara)
-
ARIA Data Visualisation module w3c/aria#991 (6 comments by @AmeliaBR, @carmacleod, @GordonSmith, @monfera)
-
Should name be required on timer, log, table? w3c/aria#1005 (5 comments by @carmacleod, @jnurthen, @zcorpan)
-
Is the attribute aria-level on role=grid and role=tablist necessary? w3c/aria#915 (4 comments by @jnurthen, @mcking65, @zcorpan)
-
Need aria-rowtext, aria-coltext for name of row/col in spreadsheet w3c/aria#667 (4 comments by @joanmarie)
-
propose an text based aria-description based on aria-label w3c/aria#992 (4 comments by @carmacleod, @DavidMacDonald, @jnurthen)
-
Revising what ARIA attributes should be considered global w3c/aria#999 (3 comments by @jnurthen, @scottaohara)
-
Tooltip role should allow referencing by aria-labelledby w3c/aria#987 (3 comments by @carmacleod, @mcking65, @scottaohara)
-
New convention for form fields with no aria-corresponding attribute. w3c/aria#1000 (2 comments by @DavidMacDonald, @stes-acc)
-
aria-sort recommendation to have it only on ONE header w3c/aria#582 (2 comments by @DavidMacDonald, @jnurthen)
-
The Combobox 1.0 design pattern references incorrectly include aria-owns instead of aria-controls. w3c/aria#998 (2 comments by @accdc, @jnurthen)
-
Undefined behavior for Element and FrozenArray<Element> reflecting IDL attributes w3c/aria#978 (1 comment by @zcorpan)
-
aria-atomic doesn't say what its missing/invalid value defaults are w3c/aria#976 (1 comment by @zcorpan)
-
Request for aria-description to set accessible description w3c/aria#891 (1 comment by @DavidMacDonald)
-
-
6 pull requests opened in the SVG Accessibility Task Force.
-
Remove advice against changing roles w3c/aria#1006, by @jnurthen.
-
Name Not Required on gridcell w3c/aria#1004, by @jnurthen.
-
Name not required for gridcell w3c/aria#1002, by @jnurthen.
-
[editorial] removed obsolete references. Resolves #983 w3c/aria#997, by @jnurthen.
-
Initial aria-textseparation (depends on generic PR being merged) w3c/aria#996, by @carmacleod.
-
Create aria-rowindextext and aria-colindextext w3c/aria#994, by @joanmarie.
-
-
5 pull requests merged in the SVG Accessibility Task Force.
-
Prohibit label on certain roles w3c/aria#985.
-
Create aria-rowindextext and aria-colindextext w3c/aria#994.
-
-
2 pull requests closed in the SVG Accessibility Task Force.
-
Name not required for gridcell w3c/aria#1002.
-
Make aria-label and labelledby non global w3c/aria#967.
-
-
1 pull request reopened in the SVG Accessibility Task Force.
-
Make aria-label and labelledby non global w3c/aria#967, by @jnurthen.
-
-
10 pull requests in the SVG Accessibility Task Force received 63 new comments.
-
Prohibit label on certain roles w3c/aria#985 (36 comments by @carmacleod, @jnurthen, @joanmarie, @mcking65, @schne324, @scottaohara, @stevefaulkner)
-
Make aria-label and labelledby non global w3c/aria#967 (4 comments by @accdc, @jeffsmith, @jnurthen, @OwenEdwards)
-
[editorial] removed obsolete references. Resolves #983 w3c/aria#997 (2 comments by @carmacleod, @jnurthen)
-
Initial aria-textseparation (depends on generic PR being merged) w3c/aria#996 (1 comment by @carmacleod)
-
GitHub
w3c/svgwg
-
6 issues opened.
-
Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents w3c/svgwg#706, by @longsonr.
-
Define "svg layout box" vs "css layout box" w3c/svgwg#703, by @AmeliaBR.
-
All links to "default sizing algorithm" are deadlink w3c/svgwg#702, by @violette77.
-
A separate MIME type for svgz files is needed w3c/svgwg#701, by @mqudsi.
-
xlink:href in <animate>, <use>, etc. doesn't work in sourceless iframes w3c/svgwg#700, by @longsonr.
-
Building a schema for SVG / Creating an SVG profile for IEC 61850-6-2 w3c/svgwg#699, by @IEC61850.
-
-
7 issues closed.
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335.
-
Scientific notation has been removed from the path EBNF w3c/svgwg#286.
-
All links to "default sizing algorithm" are deadlink w3c/svgwg#702.
-
Support transform-origin as a presentation attribute w3c/svgwg#688.
-
-
1 issue reopened.
-
Decide what to do with zoom and pan w3c/svgwg#56, by @AmeliaBR.
-
-
15 issues received 61 new comments.
-
Decide what to do with zoom and pan w3c/svgwg#56 (13 comments by @AmeliaBR, @BigBadaboom, @fsoder, @longsonr, @paradisaeidae)
-
A separate MIME type for svgz files is needed w3c/svgwg#701 (12 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @longsonr, @mqudsi, @svgeesus)
-
Revert change from SVGRect/SVGPoint/SVGMatrix to DOM equivalents w3c/svgwg#706 (10 comments by @AmeliaBR, @dirkschulze, @fsoder, @longsonr)
-
Define script element processing model w3c/svgwg#196 (4 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @svgeesus)
-
Clarify SVG Integration spec re expectations for SVG in OpenType w3c/svgwg#145 (3 comments by @AmeliaBR, @litherum, @sairuspatel)
-
[svg-native] How should currentColor be handled? w3c/svgwg#678 (3 comments by @css-meeting-bot, @dirkschulze, @svgeesus)
-
Building a schema for SVG / Creating an SVG profile for IEC 61850-6-2 w3c/svgwg#699 (3 comments by @AmeliaBR, @css-meeting-bot, @IEC61850)
-
Text with multiple x="" values should be shaped as if it was not broken w3c/svgwg#631 (2 comments by @behnam, @css-meeting-bot)
-
grammar for "closepath can substitute for final coordinate" is broken w3c/svgwg#325 (2 comments by @dirkschulze)
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335 (1 comment by @dirkschulze)
-
-
1 pull request opened.
-
Update link to default sizing algorithm. Fixes issue #702 w3c/svgwg#705, by @dirkschulze.
-
-
5 pull requests merged.
-
Added paragraph about Tiny 1.2 being deprecated (bug #199) w3c/svgwg#643.
-
Align path number parsing with CSS Numbers. Fixes #331 w3c/svgwg#697.
-
Update link to default sizing algorithm. Fixes issue #702 w3c/svgwg#705.
-
-
4 pull requests received 5 new comments.
-
'd' presentation attribute: use path() function w3c/svgwg#374 (2 comments by @css-meeting-bot, @svgeesus)
-
Add mask-type to list of presentation attributes. Fixes issue #692 w3c/svgwg#693 (1 comment by @dirkschulze)
-
Add transform-origin to list of presentation attributes. Fixes #688 w3c/svgwg#694 (1 comment by @dirkschulze)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
13 issues opened in the SVG Accessibility Task Force.
-
Suggest disallowing aria-disabled on role="link" w3c/aria#990, by @mfairchild365.
-
Spec is unclear on aria-invalid="spelling" | "grammar" uses w3c/aria#989, by @aleventhal.
-
Tooltip role should allow referencing by aria-labelledby w3c/aria#987, by @carmacleod.
-
Is the text that prohibits changing roles obsolete? w3c/aria#986, by @jnurthen.
-
remove references to XForms w3c/aria#983, by @jnurthen.
-
Clarify the use of role=tooltip w3c/aria#979, by @scottaohara.
-
Remove Appendix A Schemata? w3c/aria#977, by @zcorpan.
-
aria-atomic doesn't say what its missing/invalid value defaults are w3c/aria#976, by @zcorpan.
-
Remove references to SMIL w3c/aria#973, by @carmacleod.
-
Fix association of definition and term roles w3c/aria#970, by @jnurthen.
-
-
7 issues closed in the SVG Accessibility Task Force.
-
Avoid XML-specific terminology "IDREF" w3c/aria#952.
-
Remove Appendix A Schemata? w3c/aria#977.
-
Remove references to SMIL w3c/aria#973.
-
Consider allowing aria-required on checkboxes w3c/aria#921.
-
need code role w3c/aria#874.
-
Add aria-expanded as a supported property of listbox w3c/aria#722.
-
-
26 issues in the SVG Accessibility Task Force received 67 new comments.
-
Clarify the use of role=tooltip w3c/aria#979 (12 comments by @jnurthen, @LJWatson, @patrickhlauke, @scottaohara, @stes-acc)
-
Is the text that prohibits changing roles obsolete? w3c/aria#986 (5 comments by @accdc, @aleventhal, @jnurthen)
-
Tooltip role should allow referencing by aria-labelledby w3c/aria#987 (4 comments by @carmacleod, @scottaohara)
-
Undefined behavior for Element and FrozenArray<Element> reflecting IDL attributes w3c/aria#978 (4 comments by @alice, @jnurthen, @zcorpan)
-
Consider creation of aria-textattribute property for role parity with generic w3c/aria#960 (4 comments by @carmacleod, @css-meeting-bot, @joanmarie)
-
Browser support for element/attribute reflection? w3c/aria#957 (3 comments by @alice, @cookiecrook, @LJWatson)
-
[Role Parity] What do we do about canvas? w3c/aria#927 (3 comments by @AmeliaBR, @css-meeting-bot, @joanmarie)
-
Spec is unclear on aria-invalid="spelling" | "grammar" uses w3c/aria#989 (2 comments by @aleventhal, @jnurthen)
-
Fallback table needs a language update to reflect presence of non-required attributes w3c/aria#949 (2 comments by @melanierichards)
-
[Role Parity] What do we do about input (type=password)? w3c/aria#935 (2 comments by @jnurthen, @LJWatson)
-
Consider allowing aria-required on checkboxes w3c/aria#921 (2 comments by @css-meeting-bot, @joanmarie)
-
Need to check roles which support aria-expanded w3c/aria#681 (2 comments by @css-meeting-bot, @mcking65)
-
Consider creation of aria-inputtype property for role parity w3c/aria#962 (2 comments by @css-meeting-bot, @schne324)
-
Consider creation of aria-sectiontype property for role parity w3c/aria#963 (2 comments by @css-meeting-bot, @joanmarie)
-
Consider creation of aria-listtype for role parity with ul and ol w3c/aria#961 (2 comments by @css-meeting-bot, @joanmarie)
-
method to determine how blocks of text are separated (aria-text separation (property)) w3c/aria#699 (2 comments by @carmacleod, @schne324)
-
Update 'combobox' spec as per html spec/html-aam mapping for <select> element w3c/aria#817 (1 comment by @carmacleod)
-
Need role(s) for semantic emphasis (parity for strong and em elements) w3c/aria#905 (1 comment by @joanmarie)
-
Definition of "owned" is not strict enough; should actually be direct children, not any descendant w3c/aria#748 (1 comment by @joanmarie)
-
The ARIA 1.1 Combobox design pattern endorses unlabelled form fields as normative spec. w3c/aria#893 (1 comment by @css-meeting-bot)
-
-
8 pull requests opened in the SVG Accessibility Task Force.
-
Prohibit label on certain roles w3c/aria#985, by @jnurthen.
-
Generalize AccessibilityRole/AriaAttributes IDL w3c/aria#984, by @domenic.
-
Fix HTML syntax errors in the source w3c/aria#981, by @zcorpan.
-
Remove appendix "Schemata" w3c/aria#980, by @zcorpan.
-
Remove references to SMIL #973 w3c/aria#974, by @carmacleod.
-
Adds the code role w3c/aria#969, by @schne324.
-
-
10 pull requests merged in the SVG Accessibility Task Force.
-
Fix HTML syntax errors in the source w3c/aria#981.
-
Editorial: edit use of idref w3c/aria#964.
-
Remove appendix "Schemata" w3c/aria#980.
-
Remove implicit value of aria-level from heading role w3c/aria#942.
-
Remove references to SMIL #973 w3c/aria#974.
-
Add strong and emphasis roles w3c/aria#953.
-
Adds the code role w3c/aria#969.
-
12 pull requests in the SVG Accessibility Task Force received 53 new comments.
-
Tree Inclusion focus/activedescendant requirements need clarification… w3c/aria#950 (10 comments by @carmacleod, @cookiecrook, @jnurthen, @joanmarie, @mcking65)
-
Move some properties from "required" to "supported" on slider role w3c/aria#946 (7 comments by @melanierichards)
-
Issue504 description list roles w3c/aria#951 (6 comments by @css-meeting-bot, @jnurthen, @jongund, @schne324, @scottaohara)
-
Generalize AccessibilityRole/AriaAttributes IDL w3c/aria#984 (5 comments by @caridy, @carmacleod, @domenic, @jnurthen)
-
Use element reflection for IDREF/IDREF list w3c/aria#920 (5 comments by @alice, @carmacleod, @cookiecrook, @foolip)
-
Move some properties from "required" to "supported" on scrollbar role w3c/aria#944 (3 comments by @melanierichards)
-
fixed term and definition related concepts, added an aditional authori… w3c/aria#971 (2 comments by @carmacleod, @jnurthen)
-
Participants
-
3 organizations joined.
-
Wikimedia Foundation joined.
-
Microsoft Corporation joined.
-
TPGi joined.
-
GitHub
w3c/svgwg
-
11 issues opened.
-
An SVG interpolator for equispaced timeseries w3c/svgwg#698, by @NAThompson.
-
mask-type is not listed as a presentational attribute in SVG spec w3c/svgwg#692, by @faceless2.
-
[svg-native] Hinting support w3c/svgwg#691, by @dirkschulze.
-
What should be the initial value of "baseline-shift" property? w3c/svgwg#690, by @jarek-foksa.
-
[svg-native] Decide whether reusable graphical elements are needed w3c/svgwg#689, by @jarek-foksa.
-
Support transform-origin as a presentation attribute w3c/svgwg#688, by @AmeliaBR.
-
Internet Media type `image/svg+xml' w3c/svgwg#685, by @svgeesus.
-
[svg-native] Should a viewBox be required? w3c/svgwg#684, by @AmeliaBR.
-
-
11 issues closed.
-
Potentially invalid value for dasharray w3c/svgwg#642.
-
Remove color-rendering CSS property w3c/svgwg#647.
-
Defer HTML media elements in SVG 2.0 w3c/svgwg#563.
-
Use <dfn> for definitions w3c/svgwg#417.
-
member-svg-media-type@w3.org is no longer active w3c/svgwg#655.
-
Add color-interpolation="hsl" w3c/svgwg#653.
-
Typo in SVG media registration appendix w3c/svgwg#654.
-
-
2 issues reopened.
-
Use <dfn> for definitions w3c/svgwg#417, by @plehegar.
-
[svg2] "edit:excludefromidl" inconsistently applied during build w3c/svgwg#676, by @AmeliaBR.
-
-
30 issues received 84 new comments.
-
[svg-native] Decide whether reusable graphical elements are needed w3c/svgwg#689 (8 comments by @AmeliaBR, @BigBadaboom, @dirkschulze, @jarek-foksa, @litherum)
-
[svg-native] Which CSS concepts should be supported in presentation attributes? w3c/svgwg#681 (7 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @litherum)
-
member-svg-media-type@w3.org is no longer active w3c/svgwg#655 (5 comments by @maxnordlund, @svgeesus)
-
[svg-native] "SVG Native" isn't a great name w3c/svgwg#667 (5 comments by @AmeliaBR, @jarek-foksa, @lemzwerg, @svgeesus)
-
getBBox algorithm doesn't factor in child transforms w3c/svgwg#673 (4 comments by @AmeliaBR, @css-meeting-bot, @longsonr)
-
[svg-native] How should currentColor be handled? w3c/svgwg#678 (4 comments by @AmeliaBR, @dirkschulze, @litherum)
-
[svg2] "edit:excludefromidl" inconsistently applied during build w3c/svgwg#676 (4 comments by @AmeliaBR, @heycam)
-
[svg-native] Support for XML entities/CDATA required? w3c/svgwg#672 (4 comments by @AmeliaBR, @litherum, @svgeesus, @tabatkins)
-
BIDI reordering across multiple 'tspan' w3c/svgwg#635 (3 comments by @AmeliaBR, @css-meeting-bot, @Tavmjong)
-
[svg-native] Some useful style properties do not have corresponding style attributes w3c/svgwg#679 (3 comments by @AmeliaBR, @dirkschulze)
-
[svg-native] Limited support for filters? w3c/svgwg#675 (3 comments by @AmeliaBR, @dirkschulze, @jarek-foksa)
-
Support transform-origin as a presentation attribute w3c/svgwg#688 (3 comments by @AmeliaBR, @dirkschulze)
-
[svg-native] `overflow: scroll` is both forbidden and to behave like `hidden` w3c/svgwg#687 (3 comments by @dirkschulze, @maxnordlund, @svgeesus)
-
Definition of `transform` attribute in SVG 2 is not backward compatible to SVG 1.1 w3c/svgwg#644 (2 comments by @dirkschulze, @svgeesus)
-
Text with multiple x="" values should be shaped as if it was not broken w3c/svgwg#631 (2 comments by @AmeliaBR, @r12a)
-
What should be the initial value of "baseline-shift" property? w3c/svgwg#690 (2 comments by @dirkschulze, @fsoder)
-
[svg-native] Consider supporting some subset of CSS w3c/svgwg#658 (2 comments by @css-meeting-bot, @litherum)
-
In the website, the main draft page redirects to a directory listing w3c/svgwg#645 (1 comment by @svgeesus)
-
-
7 pull requests opened.
-
Align path number parsing with CSS Numbers. Fixes #331 w3c/svgwg#697, by @dirkschulze.
-
Add transform-origin to list of presentation attributes. Fixes #688 w3c/svgwg#694, by @dirkschulze.
-
Add mask-type to list of presentation attributes. Fixes issue #692 w3c/svgwg#693, by @dirkschulze.
-
close #655 w3c/svgwg#686, by @svgeesus.
-
desk top => desktop w3c/svgwg#682, by @ewilligers.
-
-
6 pull requests merged.
-
close #655 w3c/svgwg#686.
-
desk top => desktop w3c/svgwg#682.
-
10 pull requests received 18 new comments.
-
Align path number parsing with CSS Numbers. Fixes #331 w3c/svgwg#697 (3 comments by @AmeliaBR, @dirkschulze)
-
Added paragraph about Tiny 1.2 being deprecated (bug #199) w3c/svgwg#643 (3 comments by @AmeliaBR, @BigBadaboom, @svgeesus)
-
Remove iframe, video, audio, canvas and unknown elements due to lack … w3c/svgwg#571 (3 comments by @AmeliaBR, @svgeesus)
-
Remove color-rendering CSS property as resolved by the WG. Fixes #647 w3c/svgwg#695 (1 comment by @AmeliaBR)
-
Add transform-origin to list of presentation attributes. Fixes #688 w3c/svgwg#694 (1 comment by @AmeliaBR)
-
Add mask-type to list of presentation attributes. Fixes issue #692 w3c/svgwg#693 (1 comment by @AmeliaBR)
-
Make it more clear what the difference is between URL and <url> w3c/svgwg#565 (1 comment by @svgeesus)
-
w3c/svg-aam
-
1 issue closed.
-
Prepare new working draft (February 2018) w3c/svg-aam#3.
-
-
1 issue received 1 new comment.
Participants
-
7 organizations joined.
-
Met Office joined.
-
Mozilla Foundation joined.
-
Google LLC joined.
-
HM Government joined.
-
KDDI CORPORATION joined.
-
TetraLogical Services Ltd joined.
-
Apple Inc. joined.
-
GitHub
w3c/svgwg
-
26 issues opened.
-
[svg-native] Public test suite? w3c/svgwg#680, by @litherum.
-
[svg-native] How should currentColor be handled? w3c/svgwg#678, by @litherum.
-
[svg-native] Support for font variations? w3c/svgwg#677, by @litherum.
-
[svg2] "edit:excludefromidl" inconsistently applied during build w3c/svgwg#676, by @tidoust.
-
[svg-native] Limited support for filters? w3c/svgwg#675, by @litherum.
-
[svg-native] Should we provide a validator? w3c/svgwg#674, by @litherum.
-
getBBox algorithm doesn't factor in child transforms w3c/svgwg#673, by @AmeliaBR.
-
[svg-native] Support for XML entities/CDATA required? w3c/svgwg#672, by @dirkschulze.
-
[svg-native] inner svg, symbol or use elements supported? w3c/svgwg#671, by @dirkschulze.
-
[svg-native] support xlink:href on gradients w3c/svgwg#670, by @dirkschulze.
-
[svg-native] Consider supporting CSS Variables w3c/svgwg#668, by @litherum.
-
[svg-native] "SVG Native" isn't a great name w3c/svgwg#667, by @litherum.
-
[svg-native] Support out-of-sRGB colors w3c/svgwg#666, by @litherum.
-
[svg-native] What should the file extension be? w3c/svgwg#664, by @litherum.
-
[svg-native] Rebase on top of SVG 2 w3c/svgwg#661, by @litherum.
-
[svg-native] Consider adding masking support w3c/svgwg#659, by @litherum.
-
[svg-native] Consider supporting some subset of CSS w3c/svgwg#658, by @litherum.
-
Native profile of SVG w3c/svgwg#657, by @litherum.
-
[animation] transforms attr on paths referenced by mpath are ignored w3c/svgwg#656, by @BigBadaboom.
-
member-svg-media-type@w3.org is no longer active w3c/svgwg#655, by @maxnordlund.
-
Typo in SVG media registration appendix w3c/svgwg#654, by @maxnordlund.
-
-
1 issue closed.
-
Native profile of SVG w3c/svgwg#657.
-
-
16 issues received 77 new comments.
-
[svg-native] Support for XML entities/CDATA required? w3c/svgwg#672 (14 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @grorg, @litherum, @svgeesus)
-
[svg-native] What should the file extension be? w3c/svgwg#664 (13 comments by @AmeliaBR, @BigBadaboom, @css-meeting-bot, @dirkschulze, @jarek-foksa, @litherum, @svgeesus)
-
Native profile of SVG w3c/svgwg#657 (9 comments by @AmeliaBR, @BigBadaboom, @dirkschulze, @frivoal, @heycam, @jarek-foksa, @litherum, @svgeesus)
-
[svg-native] Consider supporting some subset of CSS w3c/svgwg#658 (8 comments by @BigBadaboom, @dirkschulze, @litherum, @svgeesus)
-
[svg-native] support xlink:href on gradients w3c/svgwg#670 (8 comments by @dirkschulze, @jarek-foksa, @litherum, @svgeesus)
-
[svg-native] Should declarations be required to be before all their uses? w3c/svgwg#669 (4 comments by @BigBadaboom, @dirkschulze, @litherum)
-
[svg-native] Consider supporting CSS Variables w3c/svgwg#668 (4 comments by @dirkschulze, @litherum)
-
[svg-native] inner svg, symbol or use elements supported? w3c/svgwg#671 (3 comments by @dirkschulze, @litherum, @svgeesus)
-
[svg-native] Some useful style properties do not have corresponding style attributes w3c/svgwg#679 (2 comments by @AmeliaBR, @litherum)
-
[svg-native] What should a browser do when it encounters one of these files w3c/svgwg#665 (2 comments by @dirkschulze, @svgeesus)
-
[svg-native] Spec uses "deleted", "removed" and "forbidden" interchangeably w3c/svgwg#662 (1 comment by @svgeesus)
-
-
1 pull request opened.
-
[svg-native] Add SVG Native as an Editor's Draft w3c/svgwg#663, by @litherum.
-
-
1 pull request merged.
-
[svg-native] Add SVG Native as an Editor's Draft w3c/svgwg#663.
-
-
1 pull request received 2 new comments.
SVG Accessibility Task Force
GitHub
w3c/aria
-
29 issues opened in the SVG Accessibility Task Force.
-
Implicit values for required properties section needs revising w3c/aria#966, by @jnurthen.
-
tabpanel - accessible name required conflicts with prose w3c/aria#965, by @jnurthen.
-
Consider creation of aria-sectiontype property for role parity w3c/aria#963, by @joanmarie.
-
Consider creation of aria-inputtype property for role parity w3c/aria#962, by @joanmarie.
-
Consider creation of aria-listtype for role parity with ul and ol w3c/aria#961, by @joanmarie.
-
aria-valuenow implicit value is always 50 for separator w3c/aria#959, by @zcorpan.
-
Proposal to surface the availability of virtualized content w3c/aria#958, by @melanierichards.
-
Browser support for element/attribute reflection? w3c/aria#957, by @LJWatson.
-
local files not generated into editor's drafts w3c/aria#955, by @jnurthen.
-
travis build fails first time every time w3c/aria#954, by @jnurthen.
-
Avoid XML-specific terminology "IDREF" w3c/aria#952, by @zcorpan.
-
Does the math role, as written, make sense? w3c/aria#940, by @joanmarie.
-
[Role Parity] What do we do about summary element? w3c/aria#939, by @joanmarie.
-
[Role Parity] What do we do about object? w3c/aria#938, by @joanmarie.
-
[Role Parity] What do we do about input (type=week)? w3c/aria#937, by @joanmarie.
-
[Role Parity] What do we do about input (type=time)? w3c/aria#936, by @joanmarie.
-
[Role Parity] What do we do about input (type=password)? w3c/aria#935, by @joanmarie.
-
[Role Parity] What do we do about input (type=month)? w3c/aria#934, by @joanmarie.
-
[Role Parity] What do we do about input (type=file)? w3c/aria#933, by @joanmarie.
-
[Role Parity] What do we do about input (type=datetime-local)? w3c/aria#932, by @joanmarie.
-
[Role Parity] What do we do about input (type=date)? w3c/aria#931, by @joanmarie.
-
[Role Parity] What do we do about input (type=color)? w3c/aria#930, by @joanmarie.
-
[Role Parity] What do we do about embed? w3c/aria#929, by @joanmarie.
-
[Role Parity] What do we do about details? w3c/aria#928, by @joanmarie.
-
[Role Parity] What do we do about canvas? w3c/aria#927, by @joanmarie.
-
Consider parity with HTML's OL "type" attribute w3c/aria#925, by @joanmarie.
-
-
9 issues closed in the SVG Accessibility Task Force.
-
travis build fails first time every time w3c/aria#954.
-
references to tabindex w3c/aria#867.
-
need role for label w3c/aria#876.
-
need role for time element w3c/aria#878.
-
Scrollbar aria-orientation required property? w3c/aria#780.
-
Role parity for html:ins and html:del w3c/aria#526.
-
36 issues in the SVG Accessibility Task Force received 123 new comments.
-
ARIA 1.1: Remove children-presentational true from math role w3c/aria#425 (13 comments by @AmeliaBR, @bkardell, @cookiecrook, @joanmarie)
-
Consider addition of property(ies) to expose braille string w3c/aria#765 (11 comments by @arnog, @cookiecrook, @jasonjgw, @joanmarie, @sinabahram)
-
Create description (was:definition) list role w3c/aria#504 (8 comments by @jnurthen, @johnfoliot, @jongund, @mcking65)
-
Need role(s) for semantic emphasis (parity for strong and em elements) w3c/aria#905 (8 comments by @jnurthen, @joanmarie, @jongund, @quasicomputational, @scottaohara)
-
Need aria-rowtext, aria-coltext for name of row/col in spreadsheet w3c/aria#667 (7 comments by @joanmarie, @mcking65, @minorninth)
-
Consider creation of aria-textattribute property for role parity with generic w3c/aria#960 (4 comments by @carmacleod, @jnurthen, @joanmarie)
-
The ARIA 1.1 Combobox design pattern endorses unlabelled form fields as normative spec. w3c/aria#893 (4 comments by @carmacleod, @stes-acc)
-
Implicit values for required properties section needs revising w3c/aria#966 (3 comments by @carmacleod, @jnurthen)
-
Consider creation of aria-inputtype property for role parity w3c/aria#962 (3 comments by @carmacleod, @joanmarie)
-
Role parity for html:ins and html:del w3c/aria#526 (3 comments by @aleventhal, @asurkov, @cookiecrook)
-
aria-valuenow implicit value is always 50 for separator w3c/aria#959 (2 comments by @melanierichards, @zcorpan)
-
Consider creation of aria-sectiontype property for role parity w3c/aria#963 (2 comments by @carmacleod, @joanmarie)
-
Fallback table needs a language update to reflect presence of non-required attributes w3c/aria#949 (2 comments by @melanierichards, @scottaohara)
-
[Role Parity] What do we do about input (type=password)? w3c/aria#935 (2 comments by @joanmarie, @LJWatson)
-
Tree Inclusion focus/activedescendant requirements need clarification w3c/aria#841 (2 comments by @carmacleod)
-
Clarification on the accessible description computation when aria-describedby refers to role="alert" w3c/aria#956 (1 comment by @mfairchild365)
-
Update required owned element for role 'combobox' and required context role for role 'option' w3c/aria#818 (1 comment by @mcking65)
-
Update 'combobox' spec as per html spec/html-aam mapping for <select> element w3c/aria#817 (1 comment by @mcking65)
-
17 pull requests opened in the SVG Accessibility Task Force.
-
Make aria-label and labelledby non global w3c/aria#967, by @jnurthen.
-
Editorial: edit use of idref w3c/aria#964, by @scottaohara.
-
Add strong and emphasis roles w3c/aria#953, by @joanmarie.
-
Issue504 description list roles w3c/aria#951, by @jongund.
-
Delete editor's note about placeholder. w3c/aria#948, by @carmacleod.
-
Remove default value for aria-expanded from combobox role w3c/aria#943, by @melanierichards.
-
Remove implicit value of aria-level from heading role w3c/aria#942, by @melanierichards.
-
Remove children-presentational=true from math role w3c/aria#941, by @joanmarie.
-
feat: aria-brailleroledescription w3c/aria#924, by @pkra.
-
feat: aria-braillelabel w3c/aria#923, by @pkra.
-
fix: add missing code markup w3c/aria#922, by @pkra.
-
-
8 pull requests merged in the SVG Accessibility Task Force.
-
Use element reflection for IDREF/IDREF list w3c/aria#920.
-
Delete editor's note about placeholder. w3c/aria#948.
-
Issue 875 need role for fieldeset/legend w3c/aria#911.
-
Remove children-presentational=true from math role w3c/aria#941.
-
Add new time role w3c/aria#895.
-
fix: add missing code markup w3c/aria#922.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
Issue 876: add draft specification for role label w3c/aria#886.
-
-
17 pull requests in the SVG Accessibility Task Force received 97 new comments.
-
Issue504 description list roles w3c/aria#951 (19 comments by @carmacleod, @jnurthen, @jongund, @scottaohara)
-
feat: aria-braillelabel w3c/aria#923 (14 comments by @carmacleod, @charmarkk, @cookiecrook, @jasonjgw, @joanmarie, @johnfoliot, @pkra)
-
Add strong and emphasis roles w3c/aria#953 (12 comments by @carmacleod, @css-meeting-bot, @joanmarie, @mcking65, @scottaohara)
-
Remove implicit value of aria-level from heading role w3c/aria#942 (8 comments by @accdc, @carmacleod, @jnurthen, @melanierichards)
-
Move some properties from "required" to "supported" on slider role w3c/aria#946 (7 comments by @carmacleod, @jnurthen, @mcking65, @melanierichards)
-
Move some properties from "required" to "supported" on scrollbar role w3c/aria#944 (5 comments by @carmacleod, @jnurthen, @mcking65, @melanierichards)
-
feat: aria-brailleroledescription w3c/aria#924 (5 comments by @charmarkk, @jasonjgw, @joanmarie, @johnfoliot, @pkra)
-
Remove default value for aria-expanded from combobox role w3c/aria#943 (4 comments by @carmacleod, @jnurthen, @melanierichards)
-
Update supported and required properties for the separator role w3c/aria#945 (3 comments by @carmacleod, @jnurthen, @melanierichards)
-
Editorial: Merge redundant points in Handling Author Errors section #845 w3c/aria#947 (3 comments by @jnurthen, @joanmarie)
-
Issue 876 role label (new pull request to remove conflicts and make MK suggested edits) w3c/aria#926 (3 comments by @carmacleod, @jnurthen, @jongund)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
6 issues opened in the SVG Accessibility Task Force.
-
Consider allowing aria-required on checkboxes w3c/aria#921, by @charmarkk.
-
Should there be an emoji role? w3c/aria#919, by @jnurthen.
-
aside vs role=note w3c/aria#918, by @pkra.
-
Aria role for step widget w3c/aria#917, by @flyinhigh.
-
Unclear sentence in editor's note in scrollbar role w3c/aria#914, by @spectranaut.
-
-
5 issues closed in the SVG Accessibility Task Force.
-
Inconsistency in rowgroup description w3c/aria#553.
-
Aria role for step widget w3c/aria#917.
-
aria-hidden content misleading w3c/aria#731.
-
Create address role w3c/aria#872.
-
16 issues in the SVG Accessibility Task Force received 41 new comments.
-
Definition of "owned" is not strict enough; should actually be direct children, not any descendant w3c/aria#748 (9 comments by @accdc, @jnurthen)
-
need role for time element w3c/aria#878 (6 comments by @css-meeting-bot, @jnurthen, @melanierichards, @pkra)
-
The Roles model introduces a potential timing problem w3c/aria#729 (5 comments by @accdc, @dylanb, @jnurthen)
-
Need role(s) for semantic emphasis (parity for strong and em elements) w3c/aria#905 (2 comments by @carmacleod, @jongund)
-
define aria attributes that include a human readable text string are translatable attributes w3c/aria#755 (1 comment by @jnurthen)
-
-
2 pull requests opened in the SVG Accessibility Task Force.
-
Use element reflection for IDREF/IDREF list w3c/aria#920, by @alice.
-
Add the deletion and insertion roles (w3c#526) w3c/aria#916, by @aleventhal.
-
-
3 pull requests merged in the SVG Accessibility Task Force.
-
Add the deletion and insertion roles (w3c#526) w3c/aria#916.
-
Add Translatable Attributes section w3c/aria#906.
-
-
7 pull requests in the SVG Accessibility Task Force received 27 new comments.
-
Issue 876: add draft specification for role label w3c/aria#886 (11 comments by @css-meeting-bot, @devarshipant, @jnurthen, @jongund, @mcking65, @melanierichards)
-
Issue 875 need role for fieldeset/legend w3c/aria#911 (5 comments by @jnurthen, @joanmarie, @jongund)
-
Use element reflection for IDREF/IDREF list w3c/aria#920 (2 comments by @BenevolentHighPriestess, @jnurthen)
-
Fix issue #553: rowgroup role-description of required context roles mismatches characteristics table w3c/aria#903 (1 comment by @joanmarie)
-
Lifecycle
-
1 charter started.
-
Chartered until 31 March 2021. Participants had to rejoin under this charter.
-
TR publications
-
2 documents published.
-
Media Access Events published as a Note. History of Media Access Events
-
SVG Filter Requirements published as a Note. History of SVG Filter Requirements
-
Participants
-
3 participants joined.
-
Tavmjong Bah (W3C Invited Experts) joined.
-
Amelia Bellamy-Royds (W3C Invited Experts) joined.
-
Chris Lilley (W3C) joined.
-
-
4 participants left.
-
Michael Cooper (W3C) left.
-
Amelia Bellamy-Royds (W3C Invited Experts) left.
-
Tavmjong Bah (W3C Invited Experts) left.
-
Chris Lilley (W3C) left.
-
-
2 organizations joined.
-
Monotype joined.
-
Adobe joined.
-
-
16 organizations left.
-
TetraLogical Services Ltd left.
-
Alibaba Group left.
-
HM Government left.
-
Boeing Company left.
-
Level Access left.
-
NIC.br - Brazilian Network Information Center left.
-
Apple Inc. left.
-
KDDI CORPORATION left.
-
Google LLC left.
-
Institut Mines-Télécom left.
-
Adobe left.
-
Opera Software AS left.
-
TPGi left.
-
Microsoft Corporation left.
-
Met Office left.
-
Mozilla Foundation left.
-
GitHub
w3c/svgwg
-
2 issues opened.
-
Add color-interpolation="hsl" w3c/svgwg#653, by @BigBadaboom.
-
Typo in the chapter 2 overview w3c/svgwg#651, by @jarek-foksa.
-
-
3 issues closed.
-
Path data: period character should be Unicode U+002E? w3c/svgwg#649.
-
SVG 2 Editor's draft is broken w3c/svgwg#646.
-
Typo in the chapter 2 overview w3c/svgwg#651.
-
-
9 issues received 28 new comments.
-
Radial gradients: "fully overlapping" vs "focal point on the edge" - which takes precedence? w3c/svgwg#648 (9 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @fsoder, @longsonr, @Tavmjong)
-
Potentially invalid value for dasharray w3c/svgwg#642 (7 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @svgeesus, @tabatkins)
-
Remove color-rendering CSS property w3c/svgwg#647 (3 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze)
-
Definition of `transform` attribute in SVG 2 is not backward compatible to SVG 1.1 w3c/svgwg#644 (2 comments by @BigBadaboom, @dirkschulze)
-
In the website, the main draft page redirects to a directory listing w3c/svgwg#645 (1 comment by @dirkschulze)
-
-
1 pull request opened.
-
Typo fix: sofware -> software w3c/svgwg#652, by @ewilligers.
-
-
2 pull requests merged.
-
Fix for #649. Incorrect Unicode code point reference w3c/svgwg#650.
-
Typo fix: sofware -> software w3c/svgwg#652.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
11 issues opened in the SVG Accessibility Task Force.
-
nested role=tree w3c/aria#910, by @pkra.
-
Clarify combobox label placement w3c/aria#909, by @carmacleod.
-
Consider new abstract role "phrase" w3c/aria#908, by @jnurthen.
-
Progressmeter/scrubber for audio/video not well handled in ARIA w3c/aria#907, by @aleventhal.
-
Question about image with alt="" and aria-label="foo" w3c/aria#902, by @DavidMacDonald.
-
Add additional details regarding the new caption role w3c/aria#901, by @joanmarie.
-
Change references from W3C to WHATWG version of HTML spec w3c/aria#900, by @jnurthen.
-
Should rowgroup really support name from: contents? w3c/aria#896, by @joanmarie.
-
3 issues closed in the SVG Accessibility Task Force.
-
Question about image with alt="" and aria-label="foo" w3c/aria#902.
-
20 issues in the SVG Accessibility Task Force received 60 new comments.
-
Need role(s) for semantic emphasis (parity for strong and em elements) w3c/aria#905 (11 comments by @a11ydoer, @carmacleod, @joanmarie, @pkra)
-
Should rowgroup really support name from: contents? w3c/aria#896 (6 comments by @aleventhal, @joanmarie)
-
Question about image with alt="" and aria-label="foo" w3c/aria#902 (3 comments by @DavidMacDonald, @jnurthen)
-
Add additional details regarding the new caption role w3c/aria#901 (3 comments by @carmacleod, @joanmarie)
-
Progressmeter/scrubber for audio/video not well handled in ARIA w3c/aria#907 (2 comments by @aleventhal)
-
Clarify use of aria-label on elements with no role w3c/aria#756 (2 comments by @garconvacher, @prlbr)
-
Consider addition of property(ies) to expose braille string w3c/aria#765 (2 comments by @garconvacher, @pkra)
-
Change references from W3C to WHATWG version of HTML spec w3c/aria#900 (2 comments by @carmacleod, @jnurthen)
-
The ARIA 1.1 Combobox design pattern endorses unlabelled form fields as normative spec. w3c/aria#893 (1 comment by @carmacleod)
-
"Placeholder for compact list of roles" appears under 5.4 Definition of Roles w3c/aria#871 (1 comment by @jnurthen)
-
Clarify whether owned-by author rules need explicit role attributes w3c/aria#772 (1 comment by @sideshowbarker)
-
-
6 pull requests opened in the SVG Accessibility Task Force.
-
Editorial: Fix invalid HTML markup in an example w3c/aria#912, by @zcorpan.
-
Issue 875 need role for fieldeset/legend w3c/aria#911, by @jongund.
-
Add Translatable Attributes section w3c/aria#906, by @jnurthen.
-
Add the subscript and superscript roles w3c/aria#904, by @joanmarie.
-
Remove contents as a supported name source for rowgroup w3c/aria#897, by @joanmarie.
-
-
4 pull requests merged in the SVG Accessibility Task Force.
-
Editorial: Fix invalid HTML markup in an example w3c/aria#912.
-
Add the subscript and superscript roles w3c/aria#904.
-
Remove contents as a supported name source for rowgroup w3c/aria#897.
-
Add 'meter' role w3c/aria#888.
-
-
7 pull requests in the SVG Accessibility Task Force received 10 new comments.
-
Issue 876: add draft specification for role label w3c/aria#886 (4 comments by @carmacleod, @jnurthen, @jongund)
-
GitHub
w3c/svgwg
-
7 issues opened.
-
Path data: period character should be Unicode U+002E? w3c/svgwg#649, by @danburzo.
-
Remove color-rendering CSS property w3c/svgwg#647, by @longsonr.
-
SVG 2 Editor's draft is broken w3c/svgwg#646, by @RazrFalcon.
-
Potentially invalid value for dasharray w3c/svgwg#642, by @pyoor.
-
-
2 issues closed.
-
CSS illegal values no longer defined w3c/svgwg#639.
-
8 issues received 25 new comments.
-
'color-interpolation' isn't used for alpha compositing w3c/svgwg#366 (7 comments by @sobotka, @svgeesus, @thomasmansencal)
-
Definition of `transform` attribute in SVG 2 is not backward compatible to SVG 1.1 w3c/svgwg#644 (5 comments by @AmeliaBR, @BigBadaboom, @upsuper)
-
What is the unit type after setting an SVGAngle or SVGLength's value w3c/svgwg#478 (4 comments by @AmeliaBR, @css-meeting-bot, @fsoder)
-
Radial gradients: "fully overlapping" vs "focal point on the edge" - which takes precedence? w3c/svgwg#648 (2 comments by @fsoder, @longsonr)
-
-
2 pull requests opened.
-
Fix for #649. Incorrect Unicode code point reference w3c/svgwg#650, by @BigBadaboom.
-
Added paragraph about Tiny 1.2 being deprecated (bug #199) w3c/svgwg#643, by @BigBadaboom.
-
-
2 pull requests merged.
-
No value is illegal w3c/svgwg#640.
-
1 pull request received 1 new comment.
SVG Accessibility Task Force
GitHub
w3c/aria
-
14 issues opened in the SVG Accessibility Task Force.
-
Range should subclass structure rather than widget w3c/aria#892, by @joanmarie.
-
Request for aria-description to set accessible description w3c/aria#891, by @backwardok.
-
Clarification does the widget role of tree support name from content w3c/aria#889, by @cpandhi.
-
label role affects the accesible name computation w3c/aria#887, by @jongund.
-
[Role Parity] need role for iframe w3c/aria#879, by @jnurthen.
-
need role for time element w3c/aria#878, by @jnurthen.
-
need role for sub and sup w3c/aria#877, by @jnurthen.
-
need role for label w3c/aria#876, by @jnurthen.
-
[Role Parity] need role for fieldset w3c/aria#875, by @jnurthen.
-
need code role w3c/aria#874, by @jnurthen.
-
Need cite role w3c/aria#873, by @jnurthen.
-
Create address role w3c/aria#872, by @jnurthen.
-
18 issues closed in the SVG Accessibility Task Force.
-
Range should subclass structure rather than widget w3c/aria#892.
-
label role affects the accesible name computation w3c/aria#887.
-
Author requirements clarification for aria-placeholder w3c/aria#541.
-
Missing role from aria-level definition w3c/aria#641.
-
Using pos-inset and aria-setsize with a toolbar w3c/aria#649.
-
Support selectors in ARIA relationships w3c/aria#745.
-
Clarify aria-hidden=false w3c/aria#736.
-
Questions regarding aria-haspopup w3c/aria#795.
-
Questions regarding dialog w3c/aria#794.
-
-
25 issues in the SVG Accessibility Task Force received 34 new comments.
-
"Placeholder for compact list of roles" appears under 5.4 Definition of Roles w3c/aria#871 (5 comments by @jnurthen, @joanmarie)
-
Clarification does the widget role of tree support name from content w3c/aria#889 (2 comments by @carmacleod, @jnurthen)
-
label role affects the accesible name computation w3c/aria#887 (2 comments by @DavidMacDonald, @jnurthen)
-
ARIA 1.1 Spec has conflict with use of alert role and aria-atomic attribute w3c/aria#849 (1 comment by @jnurthen)
-
aria-required vs required: spec mismatch between ARIA 1.1 and HTML 5.1 w3c/aria#433 (1 comment by @jnurthen)
-
Bringing user "actions" to the web (similar to VoiceOver and Switch Control custom actions) w3c/aria#762 (1 comment by @jnurthen)
-
-
11 pull requests opened in the SVG Accessibility Task Force.
-
Add new time role w3c/aria#895, by @melanierichards.
-
Change the superclass of range from widget to structure w3c/aria#894, by @joanmarie.
-
Editorial: remove list around Name From for tree w3c/aria#890, by @jnurthen.
-
Add 'meter' role w3c/aria#888, by @joanmarie.
-
Issue 876: add draft specification for role label w3c/aria#886, by @jongund.
-
Editorial?: Fix for #759 w3c/aria#885, by @jnurthen.
-
Editorial: Change add Default for to implicit values section w3c/aria#884, by @jnurthen.
-
Fix for #501 - authors MAY use "" w3c/aria#883, by @jnurthen.
-
-
9 pull requests merged in the SVG Accessibility Task Force.
-
Change the superclass of range from widget to structure w3c/aria#894.
-
Editorial: remove list around Name From for tree w3c/aria#890.
-
Fix for #501 - authors MAY use "" w3c/aria#883.
-
Editorial?: Fix for #759 w3c/aria#885.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
4 pull requests in the SVG Accessibility Task Force received 10 new comments.
-
Change the superclass of range from widget to structure w3c/aria#894 (3 comments by @joanmarie, @mcking65)
-
Move aria-level on heading role from required section to supported section w3c/aria#880 (2 comments by @jnurthen, @melanierichards)
Participants
-
1 organization joined.
-
TetraLogical Services Ltd joined.
-
GitHub
w3c/svgwg
-
8 issues opened.
-
CSS illegal values no longer defined w3c/svgwg#639, by @svgeesus.
-
BIDI reordering across multiple 'tspan' w3c/svgwg#635, by @RazrFalcon.
-
tspan and text shaping w3c/svgwg#634, by @RazrFalcon.
-
[References] Missing links to references w3c/svgwg#632, by @ewilligers.
-
Text with multiple x="" values should be shaped as if it was not broken w3c/svgwg#631, by @litherum.
-
Alignment point for text should not depend on “script” w3c/svgwg#629, by @fantasai.
-
'text-anchor' and Arabic text w3c/svgwg#628, by @RazrFalcon.
-
SVG 2 onwheel event name mismatch w3c/svgwg#627, by @AmeliaBR.
-
-
9 issues closed.
-
Wrong description of percentage units w3c/svgwg#406.
-
SVG 2 has un-used references w3c/svgwg#71.
-
Build warnings w3c/svgwg#602.
-
text-overflow definition moved from CSS UI to CSS Overflow w3c/svgwg#609.
-
[References] Missing links to references w3c/svgwg#632.
-
SVG 2 onwheel event name mismatch w3c/svgwg#627.
-
Mark 4 text properties at risk w3c/svgwg#591.
-
-
1 issue reopened.
-
Confused about 'writing-mode' with 'direction' w3c/svgwg#618, by @svgeesus.
-
-
17 issues received 70 new comments.
-
Character counting in text 'x', 'y', 'dx', 'dy', and 'rotate' attributes. w3c/svgwg#537 (9 comments by @AmeliaBR, @css-meeting-bot, @litherum, @r12a, @svgeesus)
-
Confused about 'writing-mode' with 'direction' w3c/svgwg#618 (7 comments by @css-meeting-bot, @fantasai, @svgeesus)
-
Unclear step in Text Layout Algorithm (section 11.5) w3c/svgwg#617 (4 comments by @css-meeting-bot, @faceless2, @Tavmjong)
-
'text-anchor' and Arabic text w3c/svgwg#628 (4 comments by @AmeliaBR, @css-meeting-bot, @dirkschulze, @fsoder)
-
Text with multiple x="" values should be shaped as if it was not broken w3c/svgwg#631 (3 comments by @fantasai, @litherum, @r12a)
-
Add decode() and decoding attribute to SVGImageElement w3c/svgwg#373 (3 comments by @AmeliaBR, @annevk, @chrishtr)
-
Clarify the baseline value during the top-to-bottom writing mode for Latin text w3c/svgwg#619 (2 comments by @fantasai, @svgeesus)
-
letter-spacing definition "removes" percentage - not possible w3c/svgwg#611 (1 comment by @svgeesus)
-
Remove redundant <dl> wrapper for the attribute table + prose block of each element w3c/svgwg#113 (1 comment by @svgeesus)
-
Do we really need not to reflect additional enum values in SVG 2 w3c/svgwg#424 (1 comment by @fsoder)
-
11 pull requests opened.
-
Enum-like DOM properties throw TypeErrors on setting to unknown values w3c/svgwg#641, by @AmeliaBR.
-
No value is illegal w3c/svgwg#640, by @AmeliaBR.
-
Clarify intro text re percentage units w3c/svgwg#638, by @AmeliaBR.
-
Add testing widget w3c/svgwg#636, by @svgeesus.
-
[References] Fix missing links w3c/svgwg#633, by @ewilligers.
-
Mouse wheel event attribute is onwheel w3c/svgwg#630, by @ewilligers.
-
add missing changes for DOMMatrix2DInit w3c/svgwg#626, by @svgeesus.
-
-
11 pull requests merged.
-
Clarify intro text re percentage units w3c/svgwg#638.
-
Fix #71 w3c/svgwg#637.
-
fix #609 w3c/svgwg#623.
-
Add testing widget w3c/svgwg#636.
-
[References] Fix missing links w3c/svgwg#633.
-
Mouse wheel event attribute is onwheel w3c/svgwg#630.
-
fix #591 w3c/svgwg#625.
-
fix #611 w3c/svgwg#624.
-
add missing changes for DOMMatrix2DInit w3c/svgwg#626.
-
Use DOMMatrix2DInit as parameters for methods. #326 w3c/svgwg#577.
-
Update current/former editors list w3c/svgwg#621.
-
-
8 pull requests received 28 new comments.
-
Remove iframe, video, audio, canvas and unknown elements due to lack … w3c/svgwg#571 (8 comments by @AmeliaBR, @longsonr, @svgeesus)
-