SVG Working Group - Activity
No matches.
SVG Accessibility Task Force
GitHub
w3c/aria
-
11 issues opened in the SVG Accessibility Task Force.
-
Inappropriate example in Text Equivalent Computation 2.1.2 w3c/aria#2946, by @neet.
-
Artifact positional semantics w3c/aria#2944, by @DuffJohnson.
-
Title content (not metadata) w3c/aria#2943, by @DuffJohnson.
-
Explore respec wpt test implementation w3c/aria#2940, by @daniel-montalvo.
-
too many uses of "list" in 5.2.6 w3c/aria#2939, by @pkra.
-
updating the language in Section 7 (Accessibility Tree) beyond DOM nodes w3c/aria#2938, by @pkra.
-
Add Proposed Video Poster Element to the ARIA in HTML Specification w3c/aria#2937, by @scottjehl.
-
Add Proposed Video Poster Element to HTML Accessibility API Mappings w3c/aria#2936, by @scottjehl.
-
Clarify "Allowed Accessibility Child Roles" w3c/aria#2930, by @gsnedders.
-
"API's focus event" is ambiguous w3c/aria#2925, by @cookiecrook.
-
-
5 issues closed in the SVG Accessibility Task Force.
-
ARIA content model w3c/aria#2912.
-
HTML-AAM: possible abbr attr/el confusion? w3c/aria#2343.
-
Translatable Attributes w3c/aria#2827.
-
Broken references in production w3c/aria#2907.
-
-
1 issue reopened in the SVG Accessibility Task Force.
-
HTML-AAM: possible abbr attr/el confusion? w3c/aria#2343, by @spectranaut.
-
-
34 issues in the SVG Accessibility Task Force received 49 new comments.
-
"API's focus event" is ambiguous w3c/aria#2925 (4 comments by @cookiecrook, @css-meeting-bot, @jcsteh)
-
review use of "label" (as a standalone word) w3c/aria#2904 (4 comments by @css-meeting-bot, @giacomo-petri, @spectranaut)
-
Clarify "Allowed Accessibility Child Roles" w3c/aria#2930 (3 comments by @cookiecrook, @css-meeting-bot, @pkra)
-
Should role="option" be an allowed child of role="combobox" w3c/aria#2896 (2 comments by @scottaohara)
-
TPAC 2025, ARIA F2F: update on Open UI intiatives with accessibility implications w3c/aria#2665 (2 comments by @keithamus, @smhigley)
-
From WHATWG: a11y concerns around removing the blur event on element removal w3c/aria#2920 (1 comment by @spectranaut)
-
"the age old question about whether a label should override content" w3c/aria#2569 (1 comment by @spectranaut)
-
Discussion: Should AccName split name/label from contents (descendent text node contents)? w3c/aria#2623 (1 comment by @spectranaut)
-
gathering ideas for browser dev tools improvements and what to do about them w3c/aria#2748 (1 comment by @spectranaut)
-
WG process updates to combine "evergreen approach" with wide and AC review w3c/aria#2886 (1 comment by @spectranaut)
-
From CSSWG: proposal to set ARIA attributes *on pseudo-elements only* via CSS w3c/aria#2921 (1 comment by @spectranaut)
-
role="time" lacks disambiguation (time vs. date vs. duration) for platform TTS APIs w3c/aria#2926 (1 comment by @css-meeting-bot)
-
updating the language in Section 7 (Accessibility Tree) beyond DOM nodes w3c/aria#2938 (1 comment by @css-meeting-bot)
-
aria-actions on a non-focusable ancestor behavior on descendants is undefined w3c/aria#2883 (1 comment by @cookiecrook)
-
Expose implicit ARIA semantics (browser-defaults and ElementInternals) w3c/aria#2663 (1 comment by @WilcoFiers)
-
Expanding undefined condition in "Presentational Roles Conflict Resolution" w3c/aria#2638 (1 comment by @giacomo-petri)
-
-
14 pull requests opened in the SVG Accessibility Task Force.
-
Editorial: Aria 1.2 notes cleanup w3c/aria#2949, by @daniel-montalvo.
-
Editorial: clarify sync'd notes in main, banner and contentinfo w3c/aria#2948, by @scottaohara.
-
Chore: Process updates w3c/aria#2947, by @daniel-montalvo.
-
HTML-AAM: Map image maps to ATK_ROLE_IMAGE_MAP w3c/aria#2945, by @KateZhaoTR.
-
Chore: Try wpt referencing from within respec w3c/aria#2941, by @daniel-montalvo.
-
Chore: Remove duplicate w3c/aria#2935, by @daniel-montalvo.
-
Editorial: Fix some minor typos in process document w3c/aria#2934, by @daniel-montalvo.
-
Chore: Removes obsolete call in ariaChild.js w3c/aria#2932, by @daniel-montalvo.
-
Update browser_accessibility_heuristics.md w3c/aria#2931, by @cookiecrook.
-
clarification: text nodes and allowed accessibility child roles w3c/aria#2929, by @pkra.
-
Chore: Add action to update graphics-aria ED on github w3c/aria#2924, by @daniel-montalvo.
-
-
9 pull requests merged in the SVG Accessibility Task Force.
-
Chore: Remove duplicate w3c/aria#2935.
-
Editorial: Fix some minor typos in process document w3c/aria#2934.
-
Chore: Removes obsolete call in ariaChild.js w3c/aria#2932.
-
Chore: Add action to update graphics-aria ED on github w3c/aria#2924.
-
Add aria-actions focus handling wording w3c/aria#2845.
-
Editorial: I18n considerations for translatable attributes w3c/aria#2862.
-
Chore: [Accname] Resolve ambiguity in "role" references w3c/aria#2917.
-
-
17 pull requests in the SVG Accessibility Task Force received 106 new comments.
-
Core-AAM: Add Computed Accessibility Properties section w3c/aria#2800 (26 comments by @cookiecrook, @jcsteh, @spectranaut)
-
Clarify Accessibility Parent-Child Relationships for menu, group, and menuitem w3c/aria#2483 (20 comments by @css-meeting-bot, @giacomo-petri, @pkra, @spectranaut)
-
Editorial: Security considerations (from 2869) w3c/aria#2914 (9 comments by @cookiecrook, @css-meeting-bot, @daniel-montalvo, @giacomo-petri, @simoneonofri)
-
Clarify setSize and posinSet calculation for radios w3c/aria#2919 (9 comments by @css-meeting-bot, @HaTheo, @scottaohara, @spectranaut)
-
[accname PR 235] feat: update step 2F to exclude nodes referenced by aria-actions w3c/aria#2208 (8 comments by @accdc, @cookiecrook)
-
Update a no href to map to link role w3c/aria#2863 (5 comments by @HaTheo, @lolaodelola, @scottaohara)
-
clarification: text nodes and allowed accessibility child roles w3c/aria#2929 (4 comments by @css-meeting-bot, @cyns, @giacomo-petri, @pkra)
-
Update browser_accessibility_heuristics.md w3c/aria#2931 (2 comments by @cookiecrook, @css-meeting-bot)
-
Editorial: I18n considerations for translatable attributes w3c/aria#2862 (2 comments by @css-meeting-bot, @daniel-montalvo)
-
Editorial: clarify "list" as "list of roles" in Allowed Accessibility Child roles w3c/aria#2942 (1 comment by @giacomo-petri)
-
Chore: Enable stricter tooling -- enable respec validator and some specprod validators w3c/aria#2928 (1 comment by @css-meeting-bot)
-
Chore: [Accname] Resolve ambiguity in "role" references w3c/aria#2917 (1 comment by @css-meeting-bot)
-
Lifecycle
TR publications
-
1 document published.
-
Scalable Vector Graphics (SVG) 2 published as a Candidate Recommendation Snapshot. History of Scalable Vector Graphics (SVG) 2
-
Past meetings
Participants
-
2 participants joined.
-
Robert Longson (W3C Invited Experts) joined.
-
Elad Alon (Google LLC) joined.
-
GitHub
w3c/svgwg
-
19 issues opened.
-
Units: SVG 2 no longer says that one px is one user unit w3c/svgwg#1216, by @karlcow.
-
Remove the `SVGUseElementShadowRoot` interface w3c/svgwg#1214, by @karlcow.
-
Inline event handlers in <svg:use> are not interoperable. w3c/svgwg#1211, by @emilio.
-
[editorial] Property index: cx, r, rx, x rows miss their Media cell w3c/svgwg#1206, by @karlcow.
-
[editorial] path-length: range written outside the type, `<length> [0,∞]` w3c/svgwg#1204, by @karlcow.
-
[Editorial] reorganize the other specs and move them to bikeshed w3c/svgwg#1201, by @karlcow.
-
[Editorial] move the main SVG2 from master to something else such as source w3c/svgwg#1200, by @karlcow.
-
[paths] Bearing: the formulas for relative commands are not a rotation w3c/svgwg#1198, by @karlcow.
-
Should the SVGPathData mixin allow operating on animated values? w3c/svgwg#1197, by @nikolaszimmermann.
-
Tooling for bikeshed conversion of html spec to bikeshed spec w3c/svgwg#1192, by @karlcow.
-
Setting `systemLanguage` with CSS Linked Parameters w3c/svgwg#1191, by @Crissov.
-
SVGPathElement::getPathSegmentAtLength() distance can't be NaN w3c/svgwg#1190, by @SteveBeckerMSFT.
-
16 issues closed.
-
Change the use element shadow tree to closed w3c/svgwg#363.
-
<svg:use> shadow tree shouldn't be open. w3c/svgwg#875.
-
Support ES6 script modules in SVG w3c/svgwg#1033.
-
Tooling for bikeshed conversion of html spec to bikeshed spec w3c/svgwg#1192.
-
[Editorial] Convert main specification to bikeshed w3c/svgwg#1036.
-
Support pathLength via CSS w3c/svgwg#773.
-
Interop 2027: Targeted SVG interop improvements w3c/svgwg#1184.
-
SVGPathElement::getPathSegmentAtLength() distance can't be NaN w3c/svgwg#1190.
-
`side` and `path` attributes on textPath are missing on the IDL w3c/svgwg#1086.
-
SVG Params alternative: seamless w3c/svgwg#793.
-
-
28 issues received 85 new comments.
-
Should SVGPathElement::getPathSegmentAtLength() return a segment index instead of a SVGPathSegment? w3c/svgwg#1186 (14 comments by @herrstrietzel, @karlcow, @longsonr, @SteveBeckerMSFT)
-
Script sets a negative value on a reflected attribute: "in error", or the initial value? w3c/svgwg#1210 (10 comments by @karlcow, @longsonr)
-
Should SVG image, script and feImage elements support a referrerPolicy attribute as a elements already do? w3c/svgwg#1171 (6 comments by @dirkschulze, @karlcow, @nikolaszimmermann)
-
Interop 2027: Targeted SVG interop improvements w3c/svgwg#1184 (5 comments by @karlcow, @SteveBeckerMSFT)
-
`getPathSegmentAtLength()`: Define which segment is returned at exact boundary w3c/svgwg#1129 (4 comments by @herrstrietzel, @karlcow, @SteveBeckerMSFT)
-
Inline event handlers in <svg:use> are not interoperable. w3c/svgwg#1211 (3 comments by @emilio, @karlcow)
-
Negative r, rx, ry, width, height in a CSS declaration: ignored as in CSS, not the initial value (Geometry Properties) w3c/svgwg#1202 (3 comments by @caribouW3, @karlcow)
-
Should SVGPathElement::getPathSegmentAtLength() return the base value instead of the animated value? w3c/svgwg#1194 (3 comments by @karlcow, @longsonr)
-
types.html: state that getItem returns the same object for the same index w3c/svgwg#1169 (3 comments by @dirkschulze, @karlcow, @rahulthebuilder)
-
New Interface SVGPathSegment: segments should be more editable w3c/svgwg#974 (2 comments by @longsonr, @SteveBeckerMSFT)
-
Setting `systemLanguage` with CSS Linked Parameters w3c/svgwg#1191 (2 comments by @Crissov, @karlcow)
-
SVGPathElement::getPathSegmentAtLength() distance can't be NaN w3c/svgwg#1190 (2 comments by @karlcow)
-
Consider allowing GetBBox on non-rendered elements to always return an empty rect. w3c/svgwg#1176 (2 comments by @dirkschulze, @karlcow)
-
`path` on `<textPath>` is Animatable: yes, but the path-data interpolation rule is only written for `d` w3c/svgwg#1174 (2 comments by @dirkschulze, @karlcow)
-
SVGLength value setter: the unit stays in SVG 1.1 and in all browsers, the SVG 2 draft says it goes away w3c/svgwg#1217 (1 comment by @karlcow)
-
[circle][ellipse] SVG 2 silent on valid negative values for cx/cy. see also other presentation attributes prose. w3c/svgwg#1145 (1 comment by @karlcow)
-
Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts w3c/svgwg#249 (1 comment by @karlcow)
-
[paths] Bearing: the formulas for relative commands are not a rotation w3c/svgwg#1198 (1 comment by @karlcow)
-
Specification of a new fragment identifier for the image/svg+xml media type (for use with CSS Linked Parameters) w3c/svgwg#1144 (1 comment by @Crissov)
-
-
13 pull requests opened.
-
fix #1214 - remove the SVGUseElementShadowRoot interface w3c/svgwg#1215, by @karlcow.
-
fix #363 - use-element shadow tree is closed w3c/svgwg#1213, by @karlcow.
-
fix #1208 - Negative attribute values take the initial value w3c/svgwg#1209, by @karlcow.
-
fix #1206 - Property index: add the missing Media cells w3c/svgwg#1207, by @karlcow.
-
fix #1204 - path-length: range inside the type, <length [0,∞]> w3c/svgwg#1205, by @karlcow.
-
fix #1202 - Geometry Properties: negative values follow CSS ranges w3c/svgwg#1203, by @karlcow.
-
fix #1036, fix #1192 - Switch SVG 2 to Bikeshed w3c/svgwg#1199, by @karlcow.
-
fix #1190 - getPathSegmentAtLength: drop the unreachable NaN rule w3c/svgwg#1196, by @karlcow.
-
fix #1194 - getPathSegmentAtLength reads the base value of d w3c/svgwg#1195, by @karlcow.
-
fix #1192 - Add a Bikeshed build of SVG 2, published side by side w3c/svgwg#1193, by @karlcow.
-
fix #1174 - textPath path animates like d w3c/svgwg#1189, by @karlcow.
-
fix #1171 - referrerpolicy on image and script w3c/svgwg#1188, by @karlcow.
-
fix #1033 - script follows the HTML script element w3c/svgwg#1187, by @karlcow.
-
-
11 pull requests merged.
-
fix #363 - use-element shadow tree is closed w3c/svgwg#1213.
-
fix #1206 - Property index: add the missing Media cells w3c/svgwg#1207.
-
fix #1204 - path-length: range inside the type, <length [0,∞]> w3c/svgwg#1205.
-
fix #1033 - script follows the HTML script element w3c/svgwg#1187.
-
fix #1171 - referrerpolicy on image and script w3c/svgwg#1188.
-
fix #1174 - textPath path animates like d w3c/svgwg#1189.
-
fix #1036, fix #1192 - Switch SVG 2 to Bikeshed w3c/svgwg#1199.
-
fix #1194 - getPathSegmentAtLength reads the base value of d w3c/svgwg#1195.
-
Add 'side' attribute to SVGTextPathElement IDL w3c/svgwg#1185.
-
fix #1169 - getItem returns the same object for the same index w3c/svgwg#1183.
-
-
2 pull requests closed.
-
Fix #1036 - Attempt to convert the spec to bikeshed w3c/svgwg#1039.
-
-
8 pull requests received 15 new comments.
-
fix #1033 - script follows the HTML script element w3c/svgwg#1187 (4 comments by @karlcow, @nikolaszimmermann)
-
fix #1192 - Add a Bikeshed build of SVG 2, published side by side w3c/svgwg#1193 (3 comments by @karlcow, @tidoust)
-
Remove hreflang and type IDL from SVGAElement w3c/svgwg#1108 (2 comments by @lukewarlow, @nikolaszimmermann)
-
fix #1204 - path-length: range inside the type, <length [0,∞]> w3c/svgwg#1205 (1 comment by @karlcow)
-
fix #1169 - getItem returns the same object for the same index w3c/svgwg#1183 (1 comment by @karlcow)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
24 issues opened in the SVG Accessibility Task Force.
-
Advancing ARIA IDL w3c/aria#2922, by @rahimabdi.
-
Move html-aria into monorepo? w3c/aria#2918, by @spectranaut.
-
What should "supported" be in ACD? w3c/aria#2916, by @lolaodelola.
-
Introduction to AT Driver w3c/aria#2915, by @jugglinmike.
-
ARIA content model w3c/aria#2912, by @pkra.
-
[CI] check spelling w3c/aria#2911, by @pkra.
-
Should we add constraints to radiogroup children...? w3c/aria#2910, by @spectranaut.
-
Broken references in production w3c/aria#2907, by @jugglinmike.
-
review use of "label" (as a standalone word) w3c/aria#2904, by @pkra.
-
Administrative: Change WPT meeting short link to sort by Recent w3c/aria#2902, by @cookiecrook.
-
Re: privacy review and privacy considerations w3c/aria#2898, by @sandandsnow.
-
ARIA 1.1 Superseded? w3c/aria#2897, by @bkardell.
-
Should role="option" be an allowed child of role="combobox" w3c/aria#2896, by @jnurthen.
-
update language referring to ARIA 1.2 w3c/aria#2893, by @pkra.
-
aria gh-pages: many references to other specs are currently not resolved w3c/aria#2892, by @pkra.
-
accessibility approach for two-phase view transitions w3c/aria#2891, by @davidsgrogan.
-
Deprecate aria-flowto w3c/aria#2889, by @cookiecrook.
-
-
17 issues closed in the SVG Accessibility Task Force.
-
Add automation to fail build if changes in aria/common w3c/aria#1228.
-
Add intro and context to ARIA Notify w3c/aria#2837.
-
Should we add constraints to radiogroup children...? w3c/aria#2910.
-
1.4 Prioritization w3c/aria#1884.
-
Discuss/Review ARIA relational terms w3c/aria#1914.
-
ARIA Roadmap Doc needs updating w3c/aria#2268.
-
update readme regarding roleInfo w3c/aria#2830.
-
Privacy and Security sections have no permalink ID w3c/aria#2877.
-
-
2 issues reopened in the SVG Accessibility Task Force.
-
46 issues in the SVG Accessibility Task Force received 93 new comments.
-
"accessibility descendant" in presentational role inheritance and other concerns w3c/aria#2832 (12 comments by @css-meeting-bot, @pkra, @spectranaut, @straker)
-
Should we add constraints to radiogroup children...? w3c/aria#2910 (10 comments by @css-meeting-bot, @jcsteh, @pkra, @scottaohara, @spectranaut, @twilco)
-
Should role="option" be an allowed child of role="combobox" w3c/aria#2896 (4 comments by @css-meeting-bot, @smhigley, @spectranaut)
-
Consider a mechanism to associate controls without an explicit grouping w3c/aria#1721 (4 comments by @pkra, @spectranaut)
-
aria gh-pages: many references to other specs are currently not resolved w3c/aria#2892 (4 comments by @daniel-montalvo, @pkra)
-
gathering ideas for browser dev tools improvements and what to do about them w3c/aria#2748 (3 comments by @davidsgrogan, @pkra)
-
Could a simple heading-sequence-to-tree algorithm be useful for generating document outlines? w3c/aria#2875 (3 comments by @css-meeting-bot, @keithamus, @murata2makoto)
-
Another WG spec (annotations - archived) has a misleading note/link w3c/aria#2880 (3 comments by @daniel-montalvo, @jnurthen, @spectranaut)
-
Add explicit language and direction metadata to `AriaNotificationOptions` w3c/aria#2828 (3 comments by @daniel-montalvo, @spectranaut, @xfq)
-
aria-actions on a non-focusable ancestor behavior on descendants is undefined w3c/aria#2883 (2 comments by @cookiecrook)
-
"the age old question about whether a label should override content" w3c/aria#2569 (1 comment by @spectranaut)
-
Discussion: Should AccName split name/label from contents (descendent text node contents)? w3c/aria#2623 (1 comment by @spectranaut)
-
From CSSWG: proposal to set ARIA attributes *on pseudo-elements only* via CSS w3c/aria#2921 (1 comment by @davidsgrogan)
-
From WHATWG: a11y concerns around removing the blur event on element removal w3c/aria#2920 (1 comment by @noamr)
-
Filtering a listbox with a text field (filterable select) w3c/aria#2841 (1 comment by @davidsgrogan)
-
ARIA spec is not clear on use of the role attribute and global ARIA attributes on non-HTML elements w3c/aria#2254 (1 comment by @pkra)
-
The set of roles that can serve as an OrderedSet container is not clear w3c/aria#2634 (1 comment by @pkra)
-
Specify browser structure outside of web content in accessibility APIs? w3c/aria#2890 (1 comment by @janewman)
-
aria-actions: handling focus when actions are synthetically triggered w3c/aria#2691 (1 comment by @css-meeting-bot)
-
Support an attribute like aria-posindom that lets us modify a11y tree without modifying DOM order w3c/aria#1021 (1 comment by @pkra)
-
Clarify what UAs must do when presentational elements receive global attributes w3c/aria#1474 (1 comment by @pkra)
-
-
16 pull requests opened in the SVG Accessibility Task Force.
-
Clarify setSize and posinSet calculation for radios w3c/aria#2919, by @spectranaut.
-
Chore: [Accname] Resolve ambiguity in "role" references w3c/aria#2917, by @daniel-montalvo.
-
Editorial: Security considerations (from 2869) w3c/aria#2914, by @daniel-montalvo.
-
[svg-aam] Fix name of ED parameter in ReSpec config w3c/aria#2913, by @tidoust.
-
Adjust repo names and ED URLs in ReSpec config w3c/aria#2909, by @tidoust.
-
Trigger build of Core AAM w3c/aria#2908, by @jugglinmike.
-
AX API: Update date input mapping to match WebKit w3c/aria#2901, by @spectranaut.
-
Editorial: Adds alias to be able to use target as the link text w3c/aria#2900, by @daniel-montalvo.
-
editorial: fix references for target element w3c/aria#2899, by @pkra.
-
Editorial: clarify ARIA 1.2 historical references w3c/aria#2895, by @dvd233.
-
editorial: add references to expose & target element w3c/aria#2894, by @pkra.
-
Editorial: Add Adam Page's IRC Scribe cheatsheet link w3c/aria#2888, by @cookiecrook.
-
EDITORIAL: Update onboarding.md for PDF-AAM w3c/aria#2887, by @zakkinsey.
-
editorial: update roleInfo in README w3c/aria#2885, by @pkra.
-
-
10 pull requests merged in the SVG Accessibility Task Force.
-
Editorial: ARIA Notify intro and i18n example w3c/aria#2869.
-
[svg-aam] Fix name of ED parameter in ReSpec config w3c/aria#2913.
-
Trigger build of Core AAM w3c/aria#2908.
-
Adjust repo names and ED URLs in ReSpec config w3c/aria#2909.
-
Editorial: various typos found with cSpell w3c/aria#2865.
-
editorial: update roleInfo in README w3c/aria#2885.
-
editorial: add references to expose & target element w3c/aria#2894.
-
EDITORIAL: Update onboarding.md for PDF-AAM w3c/aria#2887.
-
Editorial: Add Adam Page's IRC Scribe cheatsheet link w3c/aria#2888.
-
-
2 pull requests closed in the SVG Accessibility Task Force.
-
editorial: fix references for target element w3c/aria#2899.
-
Editorial: clarify ARIA 1.2 historical references w3c/aria#2895.
-
-
17 pull requests in the SVG Accessibility Task Force received 91 new comments.
-
Add aria-actions focus handling wording w3c/aria#2845 (29 comments by @jcsteh, @mcking65, @smhigley, @twilco)
-
Core-AAM: Add Computed Accessibility Properties section w3c/aria#2800 (11 comments by @jcsteh, @rahimabdi)
-
Editorial: I18n considerations for translatable attributes w3c/aria#2862 (10 comments by @aphillips, @daniel-montalvo, @front-endian, @pkra, @xfq)
-
Editorial: ARIA Notify intro and i18n example w3c/aria#2869 (10 comments by @css-meeting-bot, @daniel-montalvo, @janewman, @smhigley, @xfq)
-
html-aam: Specify AXTitleUIElement mappings for label, fieldset/legend, and caption w3c/aria#2905 (4 comments by @cookiecrook, @spectranaut)
-
Editorial: various typos found with cSpell w3c/aria#2865 (4 comments by @daniel-montalvo, @giacomo-petri)
-
Allow aria-valuetext for use with combobox role w3c/aria#2417 (2 comments by @css-meeting-bot, @front-endian)
-
Editorial: Update documentation on various web platform a11y testing initiatives w3c/aria#2839 (1 comment by @rahimabdi)
-
Past meetings
Participants
-
3 participants joined.
-
Gabriel Brito (Microsoft Corporation) joined.
-
Rahul Singh (Microsoft Corporation) joined.
-
Virali Purbey (Microsoft Corporation) joined.
-
-
1 participant left.
-
Léonie Watson (TetraLogical Services Ltd) left.
-
-
1 organization left.
-
TetraLogical Services Ltd left.
-
GitHub
w3c/svgwg
-
13 issues opened.
-
Interop 2027: Targeted SVG interop improvements w3c/svgwg#1184, by @SteveBeckerMSFT.
-
Why does `text` not allow specifying `x` and `y` in CSS? w3c/svgwg#1181, by @Zearin.
-
Add drawable attribute to SVGElement w3c/svgwg#1180, by @schenney-chromium.
-
`getTotalLength()` in the context of `textPath` element with an `href` w3c/svgwg#1178, by @karlcow.
-
SVG Path API should reject flags with values other than 0 or 1 w3c/svgwg#1177, by @longsonr.
-
[meta] Consider having the new SVGPathElement API on SVGTextPathElement w3c/svgwg#1175, by @longsonr.
-
types.html: state that getItem returns the same object for the same index w3c/svgwg#1169, by @karlcow.
-
-
3 issues closed.
-
SVGAElement implements two conflicting interfaces w3c/svgwg#312.
-
27 issues received 74 new comments.
-
What should text.x.baseVal.numberOfItems be when x is not specified? w3c/svgwg#1168 (12 comments by @caribouW3, @karlcow, @longsonr, @nikolaszimmermann)
-
Should SVG image, script and feImage elements support a referrerPolicy attribute as a elements already do? w3c/svgwg#1171 (7 comments by @annevk, @dirkschulze, @karlcow, @longsonr, @nikolaszimmermann)
-
types.html: state that getItem returns the same object for the same index w3c/svgwg#1169 (5 comments by @dirkschulze, @karlcow, @nikolaszimmermann)
-
[meta] Consider having the new SVGPathElement API on SVGTextPathElement w3c/svgwg#1175 (5 comments by @dirkschulze, @karlcow)
-
`path` on `<textPath>` is Animatable: yes, but the path-data interpolation rule is only written for `d` w3c/svgwg#1174 (4 comments by @dirkschulze, @karlcow, @nikolaszimmermann)
-
setMatrix takes DOMMatrix2DInit, which makes its is2D() branch unreachable w3c/svgwg#1155 (4 comments by @longsonr, @nikolaszimmermann)
-
Should the SVG matrix methods reject non-finite DOMMatrix2DInit values? w3c/svgwg#1154 (3 comments by @longsonr, @nikolaszimmermann)
-
SVGAElement implements two conflicting interfaces w3c/svgwg#312 (3 comments by @karlcow, @longsonr, @nikolaszimmermann)
-
points-attribute: clarify "render up to" vs. "don't render" if syntax partially correct w3c/svgwg#764 (3 comments by @longsonr, @nikolaszimmermann)
-
Is `x`/`y` a presentation attribute on `symbol`? Table and property definition disagree w3c/svgwg#1164 (2 comments by @longsonr, @nikolaszimmermann)
-
SVG 2 restores the `SVGMatrix` name (#1143) but never defines the interface w3c/svgwg#1156 (2 comments by @longsonr, @nikolaszimmermann)
-
'd' presentation attribute inconsistent with shipped implementation and offset-path w3c/svgwg#320 (1 comment by @karlcow)
-
'path-length' property repeats the zero rule without the 'non-percentage' qualifier the attribute has w3c/svgwg#1179 (1 comment by @karlcow)
-
`getTotalLength()` in the context of `textPath` element with an `href` w3c/svgwg#1178 (1 comment by @longsonr)
-
Consider allowing GetBBox on non-rendered elements to always return an empty rect. w3c/svgwg#1176 (1 comment by @karlcow)
-
[linking] Specify what an applied SVG view specification does to the DOM, and when w3c/svgwg#1163 (1 comment by @nikolaszimmermann)
-
The open-vs-closed subpath stroking rule is only in an informative note, and Gecko doesn't follow it w3c/svgwg#1161 (1 comment by @nikolaszimmermann)
-
`currentScale`'s setter doesn't say whether to limit the value, and each engine does something different w3c/svgwg#1158 (1 comment by @nikolaszimmermann)
-
What is the source of truth for geometry and transform IDL attributes? w3c/svgwg#1153 (1 comment by @nikolaszimmermann)
-
SVGTransform's setMatrix method should take a DOMMatrix2DInit w3c/svgwg#326 (1 comment by @nikolaszimmermann)
-
-
4 pull requests opened.
-
Add 'side' attribute to SVGTextPathElement IDL w3c/svgwg#1185, by @hyowon-igalia.
-
fix #1169 - getItem returns the same object for the same index w3c/svgwg#1183, by @karlcow.
-
fix #366 - define color-interpolation by way of CSS Color 4 w3c/svgwg#1173, by @karlcow.
-
fix #1168 - an absent list attribute reflects an empty list w3c/svgwg#1172, by @karlcow.
-
-
2 pull requests merged.
-
fix #1168 - an absent list attribute reflects an empty list w3c/svgwg#1172.
-
Swap SVGAElement to the new HyperlinkElementUtils w3c/svgwg#1052.
-
-
2 pull requests received 8 new comments.
-
Swap SVGAElement to the new HyperlinkElementUtils w3c/svgwg#1052 (7 comments by @karlcow, @lukewarlow)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
7 issues opened in the SVG Accessibility Task Force.
-
Another WG spec (annotations - archived) has a misleading note/link w3c/aria#2880, by @bkardell.
-
Privacy and Security sections have no permalink ID w3c/aria#2877, by @cookiecrook.
-
Skills for AI agents w3c/aria#2876, by @jnurthen.
-
AT support for meter w3c/aria#2872, by @pkra.
-
Committing roleinfo updates to main w3c/aria#2871, by @daniel-montalvo.
-
Security Horizontal Review w3c/aria#2861, by @simoneonofri.
-
-
5 issues closed in the SVG Accessibility Task Force.
-
Committing roleinfo updates to main w3c/aria#2871.
-
Missing role=presentation for "Name from prohibited" w3c/aria#2073.
-
Updating Editor Drafts URIs w3c/aria#2825.
-
-
13 issues in the SVG Accessibility Task Force received 40 new comments.
-
interactive elements contained in button? w3c/aria#2856 (10 comments by @cookiecrook, @css-meeting-bot, @giacomo-petri, @janewman, @jnurthen, @KateZhaoTR, @spectranaut)
-
Unclear purpose of `aria-valuemin` and `aria-valuemax` when `aria-valuetext` is used w3c/aria#1128 (6 comments by @css-meeting-bot, @janewman, @mcking65, @pkra, @scottaohara)
-
Add explicit language and direction metadata to `AriaNotificationOptions` w3c/aria#2828 (4 comments by @cookiecrook, @css-meeting-bot, @xfq)
-
Consider allowing aria-valuetext for combobox role w3c/aria#2382 (2 comments by @mcking65, @scottaohara)
-
Filtering a listbox with a text field (filterable select) w3c/aria#2841 (2 comments by @josepharhar, @spectranaut)
-
gathering ideas for browser dev tools improvements and what to do about them w3c/aria#2748 (1 comment by @jnurthen)
-
Expose implicit ARIA semantics (browser-defaults and ElementInternals) w3c/aria#2663 (1 comment by @gonzoblasco)
-
-
12 pull requests opened in the SVG Accessibility Task Force.
-
Editorial: Add ids for security and privacy considerations w3c/aria#2879, by @daniel-montalvo.
-
Editorial: Adds ids to existing security and privacy sections w3c/aria#2878, by @daniel-montalvo.
-
Runs roleInfo after aria ed w3c/aria#2874, by @daniel-montalvo.
-
[graphics-aam] Fix broken links to "Computed Role" in core-aam w3c/aria#2873, by @tidoust.
-
Editorial: ARIA Notify intro and i18n example w3c/aria#2869, by @daniel-montalvo.
-
Editorial: PDF-AAM import export 7 - table elements w3c/aria#2868, by @zakkinsey.
-
Editorial: various typos found with cSpell w3c/aria#2865, by @nschonni.
-
Chore: Stop triggers for DPUB TR publication w3c/aria#2864, by @daniel-montalvo.
-
Update a no href to map to link role w3c/aria#2863, by @lolaodelola.
-
Editorial: I18n considerations for translatable attributes w3c/aria#2862, by @daniel-montalvo.
-
-
9 pull requests merged in the SVG Accessibility Task Force.
-
Editorial: Add ids for security and privacy considerations w3c/aria#2879.
-
editorial: fix synonymous roles w3c/aria#2820.
-
Chore: Stop triggers for DPUB TR publication w3c/aria#2864.
-
Chore: Update ED urls in respecconfig w3c/aria#2858.
-
Chore: Update build actions w3c/aria#2848.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
Runs roleInfo after aria ed w3c/aria#2874.
-
-
16 pull requests in the SVG Accessibility Task Force received 83 new comments.
-
Editorial: I18n considerations for translatable attributes w3c/aria#2862 (17 comments by @cookiecrook, @daniel-montalvo, @jnurthen, @pkra, @xfq)
-
Core-AAM: Add Computed Accessibility Properties section w3c/aria#2800 (15 comments by @cookiecrook, @lolaodelola, @spectranaut)
-
Editorial: ARIA Notify intro and i18n example w3c/aria#2869 (12 comments by @cookiecrook, @giacomo-petri, @janewman)
-
Update a no href to map to link role w3c/aria#2863 (12 comments by @HaTheo, @lolaodelola, @spectranaut)
-
Editorial: various typos found with cSpell w3c/aria#2865 (6 comments by @daniel-montalvo, @jnurthen, @nschonni, @w3cbot)
-
CORE-AAM: Require ariaNotify announcements to be translated when the page is auto-translated w3c/aria#2860 (3 comments by @cookiecrook, @spectranaut)
-
Allow aria-valuetext for use with combobox role w3c/aria#2417 (2 comments by @css-meeting-bot, @mcking65)
-
Expectations for aria-hidden and focused elements w3c/aria#2181 (2 comments by @css-meeting-bot, @jnurthen)
-
Editorial: Add ids for security and privacy considerations w3c/aria#2879 (1 comment by @daniel-montalvo)
-
Update aria-busy to reflect relaxed accessibility child constraints when true w3c/aria#2754 (1 comment by @jnurthen)
-
Past meetings
Participants
-
2 participants left.
-
Virali Purbey (Microsoft Corporation) left.
-
Siddhartha Pandey (Microsoft Corporation) left.
-
GitHub
w3c/svgwg
-
6 issues opened.
-
What should text.x.baseVal.numberOfItems be when x is not specified? w3c/svgwg#1168, by @karlcow.
-
Allow em units in viewBox w3c/svgwg#1167, by @lisa-engineer.
-
Clarify `size` in the spec for consistency `viewport size`, `font size` w3c/svgwg#1165, by @karlcow.
-
-
4 issues closed.
-
Allow em units in viewBox w3c/svgwg#1167.
-
-
11 issues received 34 new comments.
-
points-attribute: clarify "render up to" vs. "don't render" if syntax partially correct w3c/svgwg#764 (11 comments by @karlcow, @longsonr, @nkfalseceilingdesigners-del)
-
SVG WG TPAC 2026 - Dublin, Ireland. Agenda October 25-30, 2026 w3c/svgwg#1157 (4 comments by @karlcow)
-
Revert changes for removing SVGViewSpec interface and SVGSVGElement.currentView w3c/svgwg#747 (3 comments by @karlcow, @shallawa)
-
Interaction of `x` attribute and `startOffset` in a textPath element. w3c/svgwg#265 (3 comments by @karlcow)
-
What is the source of truth for geometry and transform IDL attributes? w3c/svgwg#1153 (2 comments by @herrstrietzel, @karlcow)
-
points-attribute: whitespaces and empty strings in SVG 1.1 vs SVG 2 w3c/svgwg#763 (2 comments by @karlcow)
-
What should text.x.baseVal.numberOfItems be when x is not specified? w3c/svgwg#1168 (1 comment by @karlcow)
-
Should `width` and `height` apply to nested `svg` elements as CSS properties w3c/svgwg#1057 (1 comment by @karlcow)
-
The open-vs-closed subpath stroking rule is only in an informative note, and Gecko doesn't follow it w3c/svgwg#1161 (1 comment by @karlcow)
-
-
4 pull requests opened.
-
Editorial. fix #1165. Clarify size variable. w3c/svgwg#1166, by @karlcow.
-
fix #893 - drop the remaining segment-completing references w3c/svgwg#1162, by @karlcow.
-
Correct presentational attribute table for `height` and `width` w3c/svgwg#1160, by @Calme1709.
-
Fix typo in SVGAngle.unitType algorithm w3c/svgwg#1159, by @Calme1709.
-
-
4 pull requests merged.
-
Editorial. fix #1165. Clarify size variable. w3c/svgwg#1166.
-
Fix typo in SVGAngle.unitType algorithm w3c/svgwg#1159.
-
Clarify handling of negative values for geometry properties w3c/svgwg#1152.
-
fix #893 - drop the remaining segment-completing references w3c/svgwg#1162.
-
-
4 pull requests received 6 new comments.
-
Correct presentational attribute table for `height` and `width` w3c/svgwg#1160 (2 comments by @karlcow)
w3c/svg-aam
-
1 issue received 1 new comment.
-
svg-aam: remove mappings for SVG elements removed between SVG2 2016 CR and SVG2 2018 CR w3c/svg-aam#50 (1 comment by @dd8)
-
-
2 pull requests opened.
-
Groups shortname w3c/svg-aam#56, by @daniel-montalvo.
-
Update W3C json metadata w3c/svg-aam#55, by @daniel-montalvo.
-
-
3 pull requests merged.
-
set up redirects w3c/svg-aam#54.
-
Groups shortname w3c/svg-aam#56.
-
Update W3C json metadata w3c/svg-aam#55.
-
-
1 pull request received 1 new comment.