SVG Working Group - Activity in 2016
No matches.
SVG Accessibility Task Force
GitHub
w3c/aria
-
16 issues opened in the SVG Accessibility Task Force.
-
Potential need for a new CSS pseudo-class for role matching w3c/aria#506, by @therealglazou.
-
WAI-ARIA 1.1 and DPUB-ARIA 1.0 in BlueGriffon w3c/aria#505, by @therealglazou.
-
Create description (was:definition) list role w3c/aria#504, by @michael-n-cooper.
-
Lists should also be able to take term definitions w3c/aria#503, by @michael-n-cooper.
-
DPUB-ARIA abstract is too broad w3c/aria#502, by @TzviyaSiegman.
-
Handle abbr w3c/aria#498, by @michael-n-cooper.
-
Replace mentions of primer with Authoring Practices w3c/aria#490, by @mcking65.
-
Section 1.3 User Agent Support references UAIG 1.0 w3c/aria#489, by @mcking65.
-
[Role Parity] HTML 5.1 Ruby w3c/aria#488, by @michael-n-cooper.
-
-
10 issues closed in the SVG Accessibility Task Force.
-
CORE-AAM 1.1: Create MacOSX Mappings for aria-rowcount w3c/aria#462.
-
CORE-AAM 1.1: Create MacOSX Mappings for aria-rowindex w3c/aria#461.
-
CORE-AAM 1.1: Create MACOSX Mappings for aria-colcount w3c/aria#460.
-
dpub-noteref might be better captured as a rel w3c/aria#96.
-
Structural roles for floating boxes w3c/aria#100.
-
References to document objects (e.g., sections) w3c/aria#101.
-
spelling mistakes in the dpub accessibility api mapping w3c/aria#114.
-
22 issues in the SVG Accessibility Task Force received 44 new comments.
-
roledescription usage should not be limited to elements with defined ARIA roles w3c/aria#500 (9 comments by @cookiecrook, @mcking65, @richschwer, @stevefaulkner)
-
Potential confusion for end users and implementers: host language conflicts handled inconsistently w3c/aria#486 (6 comments by @karlgroves, @richschwer, @stevefaulkner)
-
CORE-AAM 1.1: Create macOS Mappings for aria-colindex, -rowindex, -colcount, -rowcount w3c/aria#459 (3 comments by @cookiecrook, @klown)
-
WAI-ARIA 1.1 and DPUB-ARIA 1.0 in BlueGriffon w3c/aria#505 (2 comments by @therealglazou, @TzviyaSiegman)
-
Allow null value of aria-activedescendent when element does not have DOM focus w3c/aria#501 (2 comments by @AmeliaBR, @mcking65)
-
Replace mentions of primer with Authoring Practices w3c/aria#490 (2 comments by @mcking65, @russmaxdesign)
-
CORE-AAM 1.1: verify Author Errors are supported in webkit (including aria-roledescription) w3c/aria#465 (1 comment by @cookiecrook)
-
w3c/aria#47 (1 comment by @TzviyaSiegman)
-
w3c/aria#74 (1 comment by @TzviyaSiegman)
-
-
3 pull requests opened in the SVG Accessibility Task Force.
-
one mapping-tables script that works with or without respec w3c/aria#499, by @jasonkiss.
-
Provide UIA mappings for DPUB-AAM w3c/aria#496, by @boggydigital.
-
-
1 pull request merged in the SVG Accessibility Task Force.
-
Provide UIA mappings for DPUB-AAM w3c/aria#496.
-
-
4 pull requests closed in the SVG Accessibility Task Force.
-
ACTION-2120: UIA: clean up mapping for aria-haspopup w3c/aria#467.
-
5 pull requests in the SVG Accessibility Task Force received 14 new comments.
-
ACTION-2120: UIA: clean up mapping for aria-haspopup w3c/aria#467 (8 comments by @boggydigital, @klown, @richschwer)
-
GitHub
w3c/svgwg
-
3 issues opened.
-
Marker auto-start-reverse and closed sub-paths w3c/svgwg#300, by @nikosandronikos.
-
What to do with z and w properties of DOMPoint? w3c/svgwg#299, by @BigBadaboom.
-
Add advice on how to handle className conflict in DOM? w3c/svgwg#298, by @BigBadaboom.
-
-
2 issues closed.
-
Add advice on how to handle className conflict in DOM? w3c/svgwg#298.
-
Marker auto-start-reverse and closed sub-paths w3c/svgwg#300.
-
-
4 issues received 14 new comments.
-
Add advice on how to handle className conflict in DOM? w3c/svgwg#298 (6 comments by @AmeliaBR, @nikosandronikos)
-
Marker auto-start-reverse and closed sub-paths w3c/svgwg#300 (5 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos)
-
Photoreal gradienting: Alternatives to mesh gradient w3c/svgwg#257 (2 comments by @Bablakeluke, @sdwarwick)
-
-
1 pull request opened.
-
Clarify that SVGElement.className overrides Element.className w3c/svgwg#301, by @nikosandronikos.
-
-
1 pull request merged.
SVG Accessibility Task Force
GitHub
w3c/aria
-
29 issues opened in the SVG Accessibility Task Force.
-
Feature for type of link target w3c/aria#484, by @michael-n-cooper.
-
Feature for language of linked resource w3c/aria#483, by @michael-n-cooper.
-
Need feature for href attribute w3c/aria#482, by @michael-n-cooper.
-
target for anchors w3c/aria#481, by @michael-n-cooper.
-
rel attribute values w3c/aria#480, by @michael-n-cooper.
-
aria-readonly for button role w3c/aria#479, by @kanggeon.
-
HTML <div> and <span> w3c/aria#478, by @michael-n-cooper.
-
HTML definition list and definitions w3c/aria#477, by @michael-n-cooper.
-
HTML blockquote w3c/aria#476, by @michael-n-cooper.
-
HTML pre element w3c/aria#475, by @michael-n-cooper.
-
ARIA role for HTML p w3c/aria#474, by @michael-n-cooper.
-
HTML optgroup element w3c/aria#473, by @michael-n-cooper.
-
HTML list attribute w3c/aria#472, by @michael-n-cooper.
-
HTML step attribute w3c/aria#471, by @michael-n-cooper.
-
@multiple w3c/aria#470, by @michael-n-cooper.
-
input format property w3c/aria#466, by @michael-n-cooper.
-
CORE-AAM 1.1: Create MacOSX Mappings for aria-rowcount w3c/aria#462, by @richschwer.
-
CORE-AAM 1.1: Create MacOSX Mappings for aria-rowindex w3c/aria#461, by @richschwer.
-
CORE-AAM 1.1: Create MACOSX Mappings for aria-colcount w3c/aria#460, by @richschwer.
-
CORE-AAM 1.1: Create macOS mappings for aria-details w3c/aria#458, by @richschwer.
-
CORE-AAM 1.1: Add mappings for aria-errormessage on macOS w3c/aria#457, by @richschwer.
-
CORE-AAM 1.1: Implement feed role on macOS w3c/aria#456, by @richschwer.
-
CORE-AAM: term role mappings restrict use to list item w3c/aria#455, by @jasonkiss.
-
1 issue reopened in the SVG Accessibility Task Force.
-
19 issues in the SVG Accessibility Task Force received 23 new comments.
-
ARIA 1.1: aria-expanded is not supported on menuitem roles w3c/aria#454 (3 comments by @accdc, @mcking65)
-
footer and header element context as landmarks (main element context change from parent to descendant) w3c/aria#362 (2 comments by @stevefaulkner, @Wildebrew)
-
Role Parity for semantically meaningless stylistic elements in HTML w3c/aria#485 (1 comment by @michael-n-cooper)
-
CORE-AAM 1.1: Create macOS Mappings for aria-colindex, -rowindex, -colcount, -rowcount w3c/aria#459 (1 comment by @richschwer)
-
-
4 pull requests opened in the SVG Accessibility Task Force.
-
Clarify keyshortcuts usage w3c/aria#487, by @ZoeBijl.
-
ACTION-2120: UIA: clean up mapping for aria-haspopup w3c/aria#467, by @boggydigital.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
Clarify keyshortcuts usage w3c/aria#487.
-
-
5 pull requests in the SVG Accessibility Task Force received 19 new comments.
-
ACTION-2120: UIA: clean up mapping for aria-haspopup w3c/aria#467 (4 comments by @boggydigital, @klown, @richschwer)
-
ACTION-2070: Add UIA Range Value Pattern to the range related roles in the role mapping table (e.g., slider). w3c/aria#468 (2 comments by @boggydigital, @klown)
GitHub
w3c/svgwg
-
2 issues opened.
-
patternTransform browser implementations do not match spec w3c/svgwg#293, by @AmeliaBR.
-
2 issues closed.
-
SVGUseElementShadowRoot section defines wrong IDL interface w3c/svgwg#290.
-
-
1 issue reopened.
-
7 issues received 34 new comments.
-
Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript w3c/svgwg#291 (21 comments by @AmeliaBR, @boggydigital, @bzbarsky, @foolip, @longsonr, @nikosandronikos)
-
patternTransform browser implementations do not match spec w3c/svgwg#293 (4 comments by @AmeliaBR, @nikosandronikos, @Tavmjong)
-
The expressions and illustrations in the vector effects chapter of SVG 2 CR are broken. w3c/svgwg#297 (3 comments by @AmeliaBR, @nikosandronikos)
-
SVG MIME Type (image/svg+xml) is misleading to developers w3c/svgwg#266 (3 comments by @BigBadaboom, @nikosandronikos, @paragonie-scott)
-
Interaction of `x` attribute and `startOffset` in a textPath element. w3c/svgwg#265 (1 comment by @nikosandronikos)
-
-
3 pull requests opened.
-
Make SVGUnitTypes a regular interface with only constants w3c/svgwg#295, by @foolip.
-
3 pull requests merged.
-
Make SVGUnitTypes a regular interface with only constants w3c/svgwg#295.
-
2 pull requests received 11 new comments.
-
Make SVGUnitTypes a regular interface with only constants w3c/svgwg#295 (6 comments by @AmeliaBR, @foolip, @nikosandronikos, @plehegar)
-
Copy Editing: Eradicate the usage of informal `you'; clean up surrounding text w3c/svgwg#294 (5 comments by @mfwitten, @nikosandronikos, @SebastianZ)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
5 issues opened in the SVG Accessibility Task Force.
-
ARIA 1.1: aria-expanded is not supported on menuitem roles w3c/aria#454, by @accdc.
-
graphics w3c/aria#453, by @VincentHXA.
-
New ARIA role for a <meter> element? w3c/aria#451, by @fstorr.
-
dpub: Endnote references w3c/aria#450, by @jcsteh.
-
Minor nits in PR #446 w3c/aria#447, by @cookiecrook.
-
-
76 issues closed in the SVG Accessibility Task Force.
-
WAI-ARIA 1.1: grid and table w3c/aria#81.
-
aria-describedat is still in the images of ARIA SVG, PNG w3c/aria#408.
-
graphics w3c/aria#453.
-
WAI-ARIA 1.1: Editorial comments for Sections 1 and 2 w3c/aria#329.
-
WAI-ARIA 1.1: about XML w3c/aria#321.
-
Editorial comments on WAI-ARIA 1.1 w3c/aria#77.
-
WAI-ARIA 1.1: Couple of editorial issues w3c/aria#82.
-
WAI-ARIA 1.1: Editorial comments w3c/aria#119.
-
Suggest attribute name change for aria-kbdshortcuts w3c/aria#285.
-
dpub: Endnote references w3c/aria#450.
-
HTML-AAM: IA2 and ATK mappings for input type=number w3c/aria#442.
-
HTML-AAM: MSAA+IA2 for input type=file w3c/aria#441.
-
HTML-AAM: MSAA Grouping or Pane for iframe? w3c/aria#439.
-
HTML-AAM: UIA mapping for rowspan w3c/aria#421.
-
HTML-AAM: mapping for colspan w3c/aria#420.
-
HTML-AAM: how to treat <img alt> with no value w3c/aria#381.
-
HTML-AAM check AX role mappings against webkit expected w3c/aria#375.
-
<dl> role should = list w3c/aria#371.
-
[HTML-AAM] SVG element should be role=graphics-document w3c/aria#347.
-
HTML-AAM: possible aria mapping for meter w3c/aria#344.
-
HTML-AAM: should meter be focusable? w3c/aria#327.
-
HTML-AAM: aria mapping for @hidden is blank w3c/aria#315.
-
HTML-AAM: UIA mapping for time element w3c/aria#314.
-
HTML-AAM: UIA mapping for address w3c/aria#270.
-
HTML-AAM: how to map Inner Phrasing Content for <meter>? w3c/aria#240.
-
HTML-AAM: should @longdesc be part of name calculation? w3c/aria#195.
-
HTML-AAM: determine best UIA mapping for @longdesc w3c/aria#194.
-
HTML-AAM: should @list map to aria-controls? w3c/aria#193.
-
HTML-AAM: UIA mapping for @list w3c/aria#192.
-
HTML-AAM: UIA mapping for @lang w3c/aria#191.
-
HTML-AAM: @abbr should be part of name calculation w3c/aria#181.
-
HTML-AAM: UIA mapping for <tr> w3c/aria#180.
-
HTML-AAM: should <legend> map to aria role=label? w3c/aria#173.
-
HTML-AAM: determine best UIA mapping for <kbd> w3c/aria#170.
-
HTML-AAM: mappings for dd, dt, dl seem insuficient w3c/aria#148.
-
HTML-AAM: should <dfn> map to aria role=definition? w3c/aria#144.
-
HTML-AAM: should <details> map to aria role=dialog? w3c/aria#143.
-
HTML-AAM: should <caption> map to aria role=label? w3c/aria#142.
-
-
86 issues in the SVG Accessibility Task Force received 110 new comments.
-
dpub: Endnote references w3c/aria#450 (10 comments by @cookiecrook, @jcsteh, @mattgarrish, @TzviyaSiegman)
-
New ARIA role for a <meter> element? w3c/aria#451 (6 comments by @AmeliaBR, @asurkov, @cookiecrook, @jasonkiss, @joanmarie)
-
Aria-errormessages property: what void does it fill? Cannot require aria-invalid w3c/aria#128 (3 comments by @michael-n-cooper, @richschwer)
-
macOS: Several DPUB roles should map to region, not group, so they can be landmarks. w3c/aria#435 (3 comments by @cookiecrook, @richschwer)
-
aria-describedat is still in the images of ARIA SVG, PNG w3c/aria#408 (1 comment by @michael-n-cooper)
-
Documented support for aria-multiselectable attribute on tablist not present in RDF schema. w3c/aria#229 (1 comment by @michael-n-cooper)
-
w3c/aria#48 (1 comment by @michael-n-cooper)
-
The WAI-ARIA Role, State, and Property Quick Reference is still a placeholder w3c/aria#409 (1 comment by @michael-n-cooper)
-
w3c/aria#77 (1 comment by @michael-n-cooper)
-
w3c/aria#82 (1 comment by @michael-n-cooper)
-
w3c/aria#84 (1 comment by @michael-n-cooper)
-
w3c/aria#52 (1 comment by @michael-n-cooper)
-
w3c/aria#79 (1 comment by @michael-n-cooper)
-
w3c/aria#80 (1 comment by @michael-n-cooper)
-
Definition for aria-kbdshortcuts references old specification w3c/aria#284 (1 comment by @michael-n-cooper)
-
describing the relationship between html-aam and core-aam mappings w3c/aria#402 (1 comment by @jasonkiss)
-
footer and header element context as landmarks (main element context change from parent to descendant) w3c/aria#362 (1 comment by @jasonkiss)
-
HTML-AAM: summary exposes expanded/collapsed state in MSAA+IA2 w3c/aria#443 (1 comment by @jasonkiss)
-
HTML-AAM: MSAA+IA2 for input types that map to IA2_ROLE_DATE_EDITOR w3c/aria#440 (1 comment by @jasonkiss)
-
HTML-AAM: MSAA+IA2 for header and footer with ancestor body should match w3c/aria#438 (1 comment by @jasonkiss)
-
HTML-AAM: Text vs Group mapping and accessible object behaviour in UIA w3c/aria#437 (1 comment by @jasonkiss)
-
[HTML-AAM] Should refer to HTML spec for defining column and row headers w3c/aria#376 (1 comment by @jasonkiss)
-
html-aam: name calculation doesn't seem to cover embedded controls w3c/aria#369 (1 comment by @jasonkiss)
-
HTML-AAM: determine right mappings for popup ui for date and time inputs w3c/aria#364 (1 comment by @jasonkiss)
-
HTML-AAM: determine right mappings for popup ui for input type=color w3c/aria#363 (1 comment by @jasonkiss)
-
HTML-AAM: determine right mappings for browser generated form validation error messages w3c/aria#360 (1 comment by @jasonkiss)
-
HTML-AAM: select element should map to listbox role regardless of presentation w3c/aria#359 (1 comment by @jasonkiss)
-
[HTML AAM] Mapping of 'form' element to ARIA 'form' role should only be done when element has a label w3c/aria#353 (1 comment by @jasonkiss)
-
HTML-AAM: td and tr Name and Description Computation not specified w3c/aria#352 (1 comment by @jasonkiss)
-
HTML-AAM: should aria-placeholder be used for accessible description on elements? w3c/aria#334 (1 comment by @jasonkiss)
-
HTML-AAM: (editorial) all UIA localized control types and localized landmark types should be lowercase w3c/aria#330 (1 comment by @jasonkiss)
-
HTML-AAM: need string values for all HTML form elements to plug into accname-aam step 2E w3c/aria#307 (1 comment by @jasonkiss)
-
[HTML-AAM] proscribe header/footer mappings to landmark roles w3c/aria#277 (1 comment by @jasonkiss)
-
HTML-AAM: should address be treated as seciton/landmark in AAPIs? w3c/aria#273 (1 comment by @jasonkiss)
-
HTML-AAM: (editorial) mark element UIA mapping has too much code styling w3c/aria#269 (1 comment by @jasonkiss)
-
HTML-AAM: accesskey mapping for UIA-Express, should it be different than UIA? w3c/aria#266 (1 comment by @jasonkiss)
-
HTML-AAM: Make presentation of UIA mapping properties consistent w3c/aria#252 (1 comment by @jasonkiss)
-
HTML-AAM: <datalist> used with non-textbox inputs shouldn't map to aria listbox role w3c/aria#233 (1 comment by @jasonkiss)
-
HTML-AAM: @title on <abbr> and <dfn> needs to be covered in name calculation w3c/aria#199 (1 comment by @jasonkiss)
-
HTML-AAM: consider adding note to style element that some CSS will change accessibiltiy tree w3c/aria#198 (1 comment by @jasonkiss)
-
HTML-AAM: determine how to map @accesskey <1 character to UIA w3c/aria#183 (1 comment by @jasonkiss)
-
HTML-AAM: where should label be attached to multi-control Edge <input type=file>? w3c/aria#163 (1 comment by @jasonkiss)
-
HTML-AAM: determine right UIA mapping for browser generated form validation error messages w3c/aria#160 (1 comment by @jasonkiss)
-
CORE-AAM: AXRoleDescription for "contentinfo" should be "content information" w3c/aria#155 (1 comment by @jasonkiss)
-
HTML-AAM: <dfn> UIA mapping to group with localized control type and text style w3c/aria#145 (1 comment by @jasonkiss)
-
-
3 pull requests opened in the SVG Accessibility Task Force.
-
Closes Tracker Issue 1049 w3c/aria#452, by @cookiecrook.
-
Update my affiliation w3c/aria#449, by @halindrome.
-
closes #447 w3c/aria#448, by @cookiecrook.
-
-
1 pull request merged in the SVG Accessibility Task Force.
-
Update my affiliation w3c/aria#449.
-
-
1 pull request in the SVG Accessibility Task Force received 1 new comment.
GitHub
w3c/svgwg
-
5 issues opened.
-
SVGUseElementShadowRoot section defines wrong IDL interface w3c/svgwg#290, by @cy6erGn0m.
-
Text chapter and definitions.xml still reference shape-outside w3c/svgwg#288, by @nikosandronikos.
-
1 issue closed.
-
Should the SVG 2 test suite use Shepherd? w3c/svgwg#270.
-
-
7 issues received 37 new comments.
-
Values in SVGZoomAndPan and SVGUnitTypes should be accessible to javascript w3c/svgwg#291 (20 comments by @bzbarsky, @foolip, @longsonr, @nikosandronikos)
-
SVG MIME Type (image/svg+xml) is misleading to developers w3c/svgwg#266 (7 comments by @gsnedders, @paragonie-scott, @thomassmailus)
-
Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts w3c/svgwg#249 (4 comments by @AmeliaBR, @dholbert, @jakearchibald)
-
Define how <image> and <img> deal with width & height, and media queries w3c/svgwg#289 (3 comments by @AmeliaBR, @jakearchibald)
-
-
1 pull request received 1 new comment.
-
Add text-transform property to the list of required CSS properties w3c/svgwg#251 (1 comment by @plehegar)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
15 issues opened in the SVG Accessibility Task Force.
-
remove line-height declaration from common.css w3c/aria#445, by @jasonkiss.
-
DPUB-AAM w3c/aria#444, by @richschwer.
-
HTML-AAM: summary exposes expanded/collapsed state in MSAA+IA2 w3c/aria#443, by @jasonkiss.
-
HTML-AAM: IA2 and ATK mappings for input type=number w3c/aria#442, by @jasonkiss.
-
HTML-AAM: MSAA+IA2 for input type=file w3c/aria#441, by @jasonkiss.
-
HTML-AAM: MSAA Grouping or Pane for iframe? w3c/aria#439, by @jasonkiss.
-
aria-required vs required: spec mismatch between ARIA 1.1 and HTML 5.1 w3c/aria#433, by @dd8.
-
Typo in ARIA 1.1 Authoring Guide w3c/aria#431, by @carmacleod.
-
Typo in aria-rowindex example code w3c/aria#430, by @carmacleod.
-
-
4 issues closed in the SVG Accessibility Task Force.
-
Typo in ARIA 1.1 Authoring Guide w3c/aria#431.
-
Typo in aria-rowindex example code w3c/aria#430.
-
HTML-AAM: Remove MSAA+UIA Express column w3c/aria#404.
-
1 issue reopened in the SVG Accessibility Task Force.
-
10 issues in the SVG Accessibility Task Force received 24 new comments.
-
macOS: Several DPUB roles should map to region, not group, so they can be landmarks. w3c/aria#435 (6 comments by @cookiecrook, @mattgarrish, @TzviyaSiegman)
-
[ARIA] Menubar superclass and required owned elements are not consistent with native equivalents w3c/aria#434 (4 comments by @carmacleod, @joanmarie, @klown)
-
HTML-AAM: IA2 and ATK mappings for input type=number w3c/aria#442 (3 comments by @jasonkiss, @joanmarie)
-
HTML-AAM: <dfn> UIA mapping to group with localized control type and text style w3c/aria#145 (1 comment by @jasonkiss)
-
Need a "4-way" picker to allow picking or moving an object within a 2D space w3c/aria#432 (1 comment by @AmeliaBR)
-
-
3 pull requests opened in the SVG Accessibility Task Force.
-
Issue444 w3c/aria#446, by @richschwer.
-
remove msaa+uiaexpress columns from html-aam w3c/aria#429, by @jasonkiss.
-
-
3 pull requests merged in the SVG Accessibility Task Force.
-
Issue444 w3c/aria#446.
-
remove msaa+uiaexpress columns from html-aam w3c/aria#429.
-
TR publications
-
5 documents published.
-
Scalable Vector Graphics (SVG) 2 published as a Candidate Recommendation Snapshot. History of Scalable Vector Graphics (SVG) 2
-
Web Animations published as a Working Draft. History of Web Animations
-
SVG Accessibility API Mappings published as a Working Draft. History of SVG Accessibility API Mappings
-
WAI-ARIA Graphics Module published as a Working Draft. History of WAI-ARIA Graphics Module
-
Graphics Accessibility API Mappings published as a First Public Working Draft. History of Graphics Accessibility API Mappings
-
Participants
-
1 participant joined.
-
Michael Cooper (W3C) joined.
-
GitHub
w3c/svgwg
-
31 issues opened.
-
The 'direction' property w3c/svgwg#287, by @lkemmel.
-
Scientific notation has been removed from the path EBNF w3c/svgwg#286, by @nical.
-
Sensible defaults for path initial point w3c/svgwg#285, by @LeaVerou.
-
Create a wiki page listing deferred SVG 2 features w3c/svgwg#284, by @AmeliaBR.
-
Mixed content issue when viewing GitHub-hosted spec over HTTPS w3c/svgwg#283, by @simevidas.
-
Merge CR changes into master & update to track changes vs CR w3c/svgwg#275, by @AmeliaBR.
-
SVG Text Layout Algorithm and multiple textPaths w3c/svgwg#274, by @karip.
-
Inline-blocks in text w3c/svgwg#273, by @karip.
-
TextPath for zero length single closed path causes division by zero w3c/svgwg#272, by @karip.
-
SVG Text Layout algorithm adjusts dx and dy wrong w3c/svgwg#271, by @karip.
-
Should the SVG 2 test suite use Shepherd? w3c/svgwg#270, by @nikosandronikos.
-
Establish SVG 2 test suite w3c/svgwg#269, by @nikosandronikos.
-
Add comment to SVGSVGElement IDL that deselectAll() is deprecated w3c/svgwg#268, by @SebastianZ.
-
SVG MIME Type (image/svg+xml) is misleading to developers w3c/svgwg#266, by @paragonie-scott.
-
Opacity properties should affect nothing but opacity w3c/svgwg#264, by @tobireif.
-
definition of character w3c/svgwg#263, by @r12a.
-
'typographic character' should mention grapheme clusters w3c/svgwg#262, by @r12a.
-
inline-base direction w3c/svgwg#261, by @r12a.
-
Rotating text w3c/svgwg#260, by @r12a.
-
UTF-16 code points for addressable characters w3c/svgwg#259, by @r12a.
-
Photoreal gradienting: Alternatives to mesh gradient w3c/svgwg#257, by @Bablakeluke.
-
Add attribute type to attributes appendix w3c/svgwg#256, by @SebastianZ.
-
Should writing-mode reset on <svg> w3c/svgwg#255, by @fsoder.
-
Add 'Applies to' info to attribute definition tables w3c/svgwg#254, by @SebastianZ.
-
Use vertical layout for attribute tables w3c/svgwg#253, by @SebastianZ.
-
Describe <percentage> and <number> values in Text chapter w3c/svgwg#252, by @SebastianZ.
-
-
5 issues closed.
-
Opacity properties should affect nothing but opacity w3c/svgwg#264.
-
Update all the cross-references from SVG 2 to other specs w3c/svgwg#189.
-
Should writing-mode reset on <svg> w3c/svgwg#255.
-
1 issue reopened.
-
Opacity properties should affect nothing but opacity w3c/svgwg#264, by @nikosandronikos.
-
-
32 issues received 115 new comments.
-
Opacity properties should affect nothing but opacity w3c/svgwg#264 (23 comments by @AmeliaBR, @karip, @nikosandronikos, @progers, @tabatkins, @tobireif, @trusktr)
-
Establish SVG 2 test suite w3c/svgwg#269 (11 comments by @AmeliaBR, @BigBadaboom, @gsnedders, @Ms2ger, @nikosandronikos, @Tavmjong)
-
Photoreal gradienting: Alternatives to mesh gradient w3c/svgwg#257 (8 comments by @AmeliaBR, @Bablakeluke, @nikosandronikos, @SebastianZ)
-
definition of character w3c/svgwg#263 (7 comments by @AmeliaBR, @fantasai, @nikosandronikos, @Tavmjong)
-
Rotating text w3c/svgwg#260 (7 comments by @AmeliaBR, @fantasai, @nikosandronikos, @r12a, @Tavmjong)
-
Scientific notation has been removed from the path EBNF w3c/svgwg#286 (6 comments by @AmeliaBR, @nical, @nikosandronikos, @tabatkins)
-
Sensible defaults for path initial point w3c/svgwg#285 (5 comments by @AmeliaBR, @LeaVerou, @nikosandronikos, @Tavmjong)
-
UTF-16 code points for addressable characters w3c/svgwg#259 (4 comments by @AmeliaBR, @aphillips, @nikosandronikos, @Tavmjong)
-
SVGPathSeg* etc has been removed from SVG2, but is still present in the SVGPaths spec w3c/svgwg#281 (4 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos)
-
Interaction of `x` attribute and `startOffset` in a textPath element. w3c/svgwg#265 (4 comments by @karip, @nikosandronikos, @Tavmjong)
-
Consider adding a switch to control how Addresssable Characters are treated w3c/svgwg#280 (3 comments by @AmeliaBR, @aphillips, @fsoder)
-
Clarify behaviour of getPointAtLength() and getPathSegmentAtLength() at discontinuities. w3c/svgwg#282 (3 comments by @AmeliaBR, @BigBadaboom)
-
'typographic character' should mention grapheme clusters w3c/svgwg#262 (3 comments by @nikosandronikos, @Tavmjong)
-
Should the SVG 2 test suite use Shepherd? w3c/svgwg#270 (2 comments by @gsnedders, @nikosandronikos)
-
Allow nesting filters instead of using 'in', 'in2' and 'result' attributes w3c/svgwg#258 (2 comments by @AmeliaBR, @SebastianZ)
-
Mixed content issue when viewing GitHub-hosted spec over HTTPS w3c/svgwg#283 (1 comment by @AmeliaBR)
-
Merge CR changes into master & update to track changes vs CR w3c/svgwg#275 (1 comment by @nikosandronikos)
-
TextPath for zero length single closed path causes division by zero w3c/svgwg#272 (1 comment by @Tavmjong)
-
Add comment to SVGSVGElement IDL that deselectAll() is deprecated w3c/svgwg#268 (1 comment by @nikosandronikos)
-
Define a style switch to allow one-dimensional shapes to render strokes, markers, etc. w3c/svgwg#236 (1 comment by @AmeliaBR)
-
Attributes and properties that allow <length> value should also allow <number> and <percentage> w3c/svgwg#222 (1 comment by @SebastianZ)
-
-
5 pull requests opened.
-
git cleanup w3c/svgwg#279, by @shepazu.
-
added foreignObject, SVG2 new features stub w3c/svgwg#278, by @shepazu.
-
added foreignObject, SVG2 new features stub w3c/svgwg#277, by @shepazu.
-
added foreignObject, SVG2 new features stub w3c/svgwg#276, by @shepazu.
-
fixed script reference w3c/svgwg#267, by @shepazu.
-
-
4 pull requests merged.
-
git cleanup w3c/svgwg#279.
-
added foreignObject, SVG2 new features stub w3c/svgwg#278.
-
added foreignObject, SVG2 new features stub w3c/svgwg#277.
-
fixed script reference w3c/svgwg#267.
-
-
1 pull request closed.
-
added foreignObject, SVG2 new features stub w3c/svgwg#276.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
9 issues opened in the SVG Accessibility Task Force.
-
CORE-AAM: clean up UIA mapping for aria-haspopup w3c/aria#428, by @cyns.
-
Radio Group should not have accessible name required: true w3c/aria#427, by @jnurthen.
-
Possible confusing language in WAI-ARIA 1.1 Authoring Guide w3c/aria#426, by @macgyver.
-
ARIA 1.1: Remove children-presentational true from math role w3c/aria#425, by @takenspc.
-
CORE-AAM: UIA mapping for aria-rowspan w3c/aria#422, by @cyns.
-
HTML-AAM: UIA mapping for rowspan w3c/aria#421, by @cyns.
-
HTML-AAM: mapping for colspan w3c/aria#420, by @cyns.
-
CORE-AAM: need UIA mapping for aria-autocomplete w3c/aria#419, by @cyns.
-
CORE-AAM: need UIA mapping for timer w3c/aria#418, by @cyns.
-
-
10 issues closed in the SVG Accessibility Task Force.
-
HTML-AAM: decide the fate of the UIA-Express column w3c/aria#268.
-
HTML-AAM: add note about UIA mapping to "Text" w3c/aria#177.
-
HTML-AAM: UIA mapping for <legend> w3c/aria#172.
-
HTML-AAM: add UIA LabeledBy info to input types w3c/aria#159.
-
CORE-AAM: UIA mapping for role=navigation w3c/aria#242.
-
HTML-AAM: UIA mapping for placeholder w3c/aria#340.
-
HTML-AAM: changes to UIA mark mapping w3c/aria#416.
-
HTML-AAM: changes to UIA video mapping w3c/aria#412.
-
-
13 issues in the SVG Accessibility Task Force received 25 new comments.
-
HTML-AAM: Make presentation of UIA mapping properties consistent w3c/aria#252 (3 comments by @asurkov, @jasonkiss)
-
HTML-AAM: role=status is not a good match for output element w3c/aria#309 (3 comments by @asurkov, @klown)
-
HTML-AAM: determine right mappings for popup ui for date and time inputs w3c/aria#364 (2 comments by @asurkov, @mcking65)
-
2 pull requests opened in the SVG Accessibility Task Force.
-
Notes to html role mappings w3c/aria#424, by @jasonkiss.
-
SVG-AAM: shadow DOM and related edits w3c/aria#423, by @AmeliaBR.
-
-
2 pull requests merged in the SVG Accessibility Task Force.
-
SVG-AAM: shadow DOM and related edits w3c/aria#423.
-
Notes to html role mappings w3c/aria#424.
-
-
2 pull requests closed in the SVG Accessibility Task Force.
-
DPUB-AAM: Add AXAPI role mappings w3c/aria#405.
-
"accessible" -> "accessible object" where appropriate w3c/aria#289.
-
-
2 pull requests in the SVG Accessibility Task Force received 4 new comments.
-
"accessible" -> "accessible object" where appropriate w3c/aria#289 (3 comments by @jasonkiss, @klown)
-
GitHub
w3c/svgwg
-
30 issues opened.
-
Triage all issues from Tracker w3c/svgwg#250, by @AmeliaBR.
-
Use "HTML" instead of "HTML5" w3c/svgwg#248, by @zcorpan.
-
x/y/width/height attributes on HTML elements w3c/svgwg#247, by @zcorpan.
-
Support SVG 1.1 baseline value for baseline-shift w3c/svgwg#246, by @nikosandronikos.
-
Correct syntax for viewBox to allow comma-separated numbers w3c/svgwg#244, by @AmeliaBR.
-
Cut down number of categories w3c/svgwg#242, by @nikosandronikos.
-
Marked-up text from other namespaces in <title> and <desc> w3c/svgwg#241, by @BigBadaboom.
-
Require HTML 5 parser to correctly parse embedded HTML elements w3c/svgwg#240, by @AmeliaBR.
-
Do min/max-width/height properties constrain SVG geometry? w3c/svgwg#238, by @AmeliaBR.
-
SVG Image size conflicts with size property and CSS style w3c/svgwg#237, by @shanmuga-m.
-
Define equivalent paths for degenerate shapes w3c/svgwg#235, by @AmeliaBR.
-
rootElement IDL attribute type should allow null w3c/svgwg#234, by @heycam.
-
Mark "paint-order" property as inheritable in the property index w3c/svgwg#232, by @jarek-foksa.
-
Consider removal SVGViewElement and its interface w3c/svgwg#231, by @shanmuga-m.
-
Adjust stroke/fill to be compatible with proposed Fill & Stroke spec w3c/svgwg#230, by @fantasai.
-
Add <use> to the graphics elements category w3c/svgwg#229, by @jarek-foksa.
-
Consider if XSL references can be removed w3c/svgwg#227, by @shepazu.
-
image-rendering property should apply to <image>, not shapes w3c/svgwg#226, by @jarek-foksa.
-
Tidy up attributes appendix w3c/svgwg#225, by @jarek-foksa.
-
Remove support for "rev" attribute on <a> element w3c/svgwg#224, by @jarek-foksa.
-
Geometry properties should allow <number> value w3c/svgwg#223, by @jarek-foksa.
-
Provide text-to-path-data conversion method w3c/svgwg#221, by @AmeliaBR.
-
-
18 issues closed.
-
Use "HTML" instead of "HTML5" w3c/svgwg#248.
-
x/y/width/height attributes on HTML elements w3c/svgwg#247.
-
Correct syntax for viewBox to allow comma-separated numbers w3c/svgwg#244.
-
Marked-up text from other namespaces in <title> and <desc> w3c/svgwg#241.
-
Do min/max-width/height properties constrain SVG geometry? w3c/svgwg#238.
-
SVG Image size conflicts with size property and CSS style w3c/svgwg#237.
-
image-rendering property should apply to <image>, not shapes w3c/svgwg#226.
-
Remove support for "rev" attribute on <a> element w3c/svgwg#224.
-
Consider removal SVGViewElement and its interface w3c/svgwg#231.
-
Define equivalent paths for degenerate shapes w3c/svgwg#235.
-
rootElement IDL attribute type should allow null w3c/svgwg#234.
-
Geometry properties should allow <number> value w3c/svgwg#223.
-
Update getNumberOfChars() definition w3c/svgwg#200.
-
-
1 issue reopened.
-
We should define the behavior of ‘use’ in terms of Web Components w3c/svgwg#99, by @shepazu.
-
-
26 issues received 82 new comments.
-
Define equivalent paths for degenerate shapes w3c/svgwg#235 (14 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos, @tabatkins)
-
Add <use> to the graphics elements category w3c/svgwg#229 (6 comments by @AmeliaBR, @jarek-foksa, @nikosandronikos)
-
Consider removal SVGViewElement and its interface w3c/svgwg#231 (6 comments by @AmeliaBR, @BigBadaboom, @jarek-foksa, @nikosandronikos, @shanmuga-m)
-
Spec synthesis of viewBox/preserveAspectRatio for viewBox-less SVGs in image contexts w3c/svgwg#249 (5 comments by @AmeliaBR, @fsoder, @nikosandronikos)
-
Marked-up text from other namespaces in <title> and <desc> w3c/svgwg#241 (4 comments by @AmeliaBR, @BigBadaboom)
-
Require HTML 5 parser to correctly parse embedded HTML elements w3c/svgwg#240 (4 comments by @AmeliaBR, @fsoder)
-
Should bounding box of svg, image, foreignObject, etc include overflow content? w3c/svgwg#243 (3 comments by @AmeliaBR, @nikosandronikos)
-
SVG Image size conflicts with size property and CSS style w3c/svgwg#237 (3 comments by @AmeliaBR, @nikosandronikos)
-
Remove support for "rev" attribute on <a> element w3c/svgwg#224 (3 comments by @AmeliaBR, @tabatkins)
-
Should some SVG 2 list type syntax definitions include a trailing comma? w3c/svgwg#233 (3 comments by @AmeliaBR, @tabatkins)
-
Adjust stroke/fill to be compatible with proposed Fill & Stroke spec w3c/svgwg#230 (3 comments by @AmeliaBR)
-
We should define the behavior of ‘use’ in terms of Web Components w3c/svgwg#99 (3 comments by @AmeliaBR, @shepazu)
-
Do min/max-width/height properties constrain SVG geometry? w3c/svgwg#238 (2 comments by @AmeliaBR, @nikosandronikos)
-
Define how object-fit and object-position interact with preserveAspectRatio w3c/svgwg#239 (2 comments by @AmeliaBR)
-
"paint-order" property should apply to the same elements as "fill" and "stroke" properties w3c/svgwg#228 (2 comments by @AmeliaBR, @nikosandronikos)
-
Attributes and properties that allow <length> value should also allow <number> and <percentage> w3c/svgwg#222 (2 comments by @AmeliaBR, @jarek-foksa)
-
Add stub pages to SVG 2 for chapters that have been moved to separate specs w3c/svgwg#195 (1 comment by @AmeliaBR)
-
Consider rewriting 'references to external resources' processing mode feature w3c/svgwg#245 (1 comment by @AmeliaBR)
-
-
1 pull request opened.
-
Add text-transform property to the list of required CSS properties w3c/svgwg#251, by @BigBadaboom.
-
-
1 pull request received 7 new comments.
-
Add text-transform property to the list of required CSS properties w3c/svgwg#251 (7 comments by @AmeliaBR, @BigBadaboom, @Tavmjong)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
8 issues opened in the SVG Accessibility Task Force.
-
HTML-AAM: changes to UIA mark mapping w3c/aria#416, by @cyns.
-
Tab panel doesn't use role=application, but example does w3c/aria#415, by @DavidMacDonald.
-
HTML-AAM: placeholder doesn't map to aria-placeholder for UIA w3c/aria#413, by @cyns.
-
HTML-AAM: changes to UIA video mapping w3c/aria#412, by @cyns.
-
aria-describedat is still in the images of ARIA SVG, PNG w3c/aria#408, by @DavidMacDonald.
-
-
2 issues closed in the SVG Accessibility Task Force.
-
WAI-ARIA 1.1: Needs to update link to SIML w3c/aria#320.
-
-
4 issues in the SVG Accessibility Task Force received 8 new comments.
-
Confusing notation in definition of attributes introduced in ARIA 1.1 w3c/aria#406 (4 comments by @joanmarie, @LJWatson, @ZoeBijl)
-
HTML-AAM: add localized control type to UIA mapping for non-landmark headers and footers (not child of body) w3c/aria#372 (1 comment by @cyns)
-
footer and header element context as landmarks (main element context change from parent to descendant) w3c/aria#362 (1 comment by @jasonkiss)
-
-
5 pull requests opened in the SVG Accessibility Task Force.
-
Uia updates w3c/aria#410, by @cyns.
-
completed action 2070 w3c/aria#407, by @cyns.
-
DPUB-AAM: Add AXAPI role mappings w3c/aria#405, by @joanmarie.
-
3 pull requests merged in the SVG Accessibility Task Force.
-
Uia updates w3c/aria#410.
-
Uia w3c/aria#414.
-
#416 Mark w3c/aria#417.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
Migrated to latest terms cleanup code w3c/aria#264.
-
-
2 pull requests in the SVG Accessibility Task Force received 3 new comments.
Participants
-
1 organization joined.
-
Ministerio do Planejamento Orcamento e Gestao joined.
-
GitHub
w3c/svgwg
-
36 issues opened.
-
Add titles and lang attributes to all SVG example files w3c/svgwg#220, by @AmeliaBR.
-
Use consistent formatting & markup for attribute definitions w3c/svgwg#219, by @AmeliaBR.
-
Indicate which elements need preserved state for DOM cloning w3c/svgwg#218, by @AmeliaBR.
-
Define behaviour of `<stop>` if `offset` value not specified. w3c/svgwg#217, by @BigBadaboom.
-
Update SVG WG Feedback page on w3.org to point to GitHub issues w3c/svgwg#216, by @AmeliaBR.
-
7.2 equivalent transform of an SVG viewport is mathematically wrong w3c/svgwg#215, by @AmeliaBR.
-
Add a load event when tree for use element is generated? w3c/svgwg#214, by @nikosandronikos.
-
Add restrictions / warnings about invalid `id` values w3c/svgwg#213, by @AmeliaBR.
-
Specify that aria states & properties are animatable w3c/svgwg#212, by @AmeliaBR.
-
Specify which attributes/properties are horizontal vs vertical vs other w3c/svgwg#211, by @AmeliaBR.
-
Allow transforms on textPath w3c/svgwg#210, by @karip.
-
Change definition of percentages to match implementations w3c/svgwg#209, by @AmeliaBR.
-
Synchronize SVGImageElement with HTMLImageElement w3c/svgwg#208, by @AmeliaBR.
-
Define a vector-only processing mode w3c/svgwg#204, by @AmeliaBR.
-
[i18n] Language fragment identifier for conditional processing w3c/svgwg#201, by @Crissov.
-
Update getNumberOfChars() definition w3c/svgwg#200, by @jarek-foksa.
-
References to editor draft specifications. w3c/svgwg#198, by @Tavmjong.
-
Define all cases for intrinsic ratio w3c/svgwg#197, by @nikosandronikos.
-
Define script element processing model w3c/svgwg#196, by @nikosandronikos.
-
Fix TOC styling in Editor's Drafts for specs on svgwg.org w3c/svgwg#194, by @AmeliaBR.
-
Clarify effect of invalid values for width & height on <use> elements w3c/svgwg#193, by @AmeliaBR.
-
Incorrect syntax for <tspan>´s attributes w3c/svgwg#191, by @SebastianZ.
-
Update percentage types to the new convenience notations w3c/svgwg#190, by @nikosandronikos.
-
Update all the cross-references from SVG 2 to other specs w3c/svgwg#189, by @AmeliaBR.
-
Remove or add warnings to outdated draft specs on dev.w3.org w3c/svgwg#188, by @AmeliaBR.
-
Define interaction of markerUnits="strokeWidth" and non-scaling-stroke w3c/svgwg#187, by @AmeliaBR.
-
Mark unimplemented vector-effects options as at risk w3c/svgwg#186, by @AmeliaBR.
-
Add an option to <use> elements to create independent, unlinked clones w3c/svgwg#184, by @AmeliaBR.
-
Define whether <use> shadow tree is interactive w3c/svgwg#183, by @AmeliaBR.
-
-
35 issues closed.
-
lengthAdjust="spacingAndGlyphs" is a BAD idea w3c/svgwg#152.
-
Allow transforms on textPath w3c/svgwg#210.
-
Mark unimplemented vector-effects options as at risk w3c/svgwg#186.
-
Add restrictions / warnings about invalid `id` values w3c/svgwg#213.
-
Specify that aria states & properties are animatable w3c/svgwg#212.
-
Deprecate <cursor> element w3c/svgwg#174.
-
Use a single-case name for meshGradient w3c/svgwg#181.
-
Define whether <use> shadow tree is interactive w3c/svgwg#183.
-
Does conditional processing mute sound playback? w3c/svgwg#44.
-
Need to update SVG 2 text layout algorithm w3c/svgwg#166.
-
Change definition of percentages to match implementations w3c/svgwg#209.
-
Define all cases for intrinsic ratio w3c/svgwg#197.
-
Incorrect syntax for <tspan>´s attributes w3c/svgwg#191.
-
Restore SVGSVGElement.prototype.getElementById w3c/svgwg#182.
-
Better error handling for nested links w3c/svgwg#178.
-
2 issues reopened.
-
Use a single-case name for meshGradient w3c/svgwg#181, by @Tavmjong.
-
Restore SVGSVGElement.prototype.getElementById w3c/svgwg#182, by @nikosandronikos.
-
-
45 issues received 145 new comments.
-
Allow transforms on textPath w3c/svgwg#210 (19 comments by @AmeliaBR, @fsoder, @karip, @nikosandronikos, @Tavmjong)
-
Update getNumberOfChars() definition w3c/svgwg#200 (14 comments by @AmeliaBR, @jarek-foksa, @nikosandronikos, @Tavmjong)
-
Clarify meaning of context-fill & context-stroke keywords in paint definitions w3c/svgwg#203 (10 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos)
-
Restore SVGSVGElement.prototype.getElementById w3c/svgwg#182 (10 comments by @AmeliaBR, @annevk, @BigBadaboom, @erikdahlstrom, @foolip, @nikosandronikos)
-
Incorrect syntax for <tspan>´s attributes w3c/svgwg#191 (8 comments by @AmeliaBR, @nikosandronikos, @SebastianZ, @tabatkins)
-
Check whether behaviour of new CSS3 units needs clarification in SVG context w3c/svgwg#207 (6 comments by @AmeliaBR, @BigBadaboom, @SebastianZ)
-
What should happen regarding 1.2 Tiny features that are not mentioned in SVG2 spec? w3c/svgwg#199 (6 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos)
-
Use a single-case name for meshGradient w3c/svgwg#181 (5 comments by @AmeliaBR, @annevk, @nikosandronikos, @Tavmjong)
-
7.2 equivalent transform of an SVG viewport is mathematically wrong w3c/svgwg#215 (4 comments by @ccprog, @nikosandronikos)
-
Use CSS gradient rules for transitioning semi-transparent stop-colors w3c/svgwg#180 (4 comments by @AmeliaBR, @nikosandronikos, @SebastianZ)
-
Does conditional processing mute sound playback? w3c/svgwg#44 (4 comments by @AmeliaBR, @karip, @nikosandronikos)
-
Update href attribute descriptions to reference HTML51's obtain the resource algorithm w3c/svgwg#90 (3 comments by @AmeliaBR)
-
Allow stroke-dasharray/dashoffset % to be specified relative to path length w3c/svgwg#177 (3 comments by @AmeliaBR, @Tavmjong)
-
Change definition of percentages to match implementations w3c/svgwg#209 (3 comments by @AmeliaBR, @nikosandronikos)
-
Define what element is returned by SVGSVGElement.getElementById when id duplicated w3c/svgwg#185 (3 comments by @annevk, @foolip, @nikosandronikos)
-
[i18n] Language fragment identifier for conditional processing w3c/svgwg#201 (2 comments by @AmeliaBR, @Crissov)
-
Allow percentages in fill-opacity, stroke-opacity, & stop-opacity, to match CSS WG changes w3c/svgwg#205 (2 comments by @AmeliaBR, @tabatkins)
-
Clarify effect of invalid values for width & height on <use> elements w3c/svgwg#193 (2 comments by @AmeliaBR, @nikosandronikos)
-
Use !important UA stylesheet rule to override display property for never-rendered elements w3c/svgwg#192 (2 comments by @AmeliaBR, @nikosandronikos)
-
Mark unimplemented vector-effects options as at risk w3c/svgwg#186 (2 comments by @AmeliaBR, @BigBadaboom)
-
Shorter equivalent path for the <rect> element w3c/svgwg#154 (2 comments by @AmeliaBR, @nikosandronikos)
-
Add an option to <use> elements to create independent, unlinked clones w3c/svgwg#184 (2 comments by @AmeliaBR, @progers)
-
SVG element names should not mix camelCase and lowercase notations w3c/svgwg#161 (1 comment by @nikosandronikos)
-
Review content model and allowed attributes on all elements w3c/svgwg#93 (1 comment by @nikosandronikos)
-
Update SVG DOM object initialisation to reflect promoted properties w3c/svgwg#85 (1 comment by @nikosandronikos)
-
Can we update image's href attribute description to reference HTML51's obtain the resource algorithm? w3c/svgwg#88 (1 comment by @AmeliaBR)
-
Remove redundant <dl> wrapper for the attribute table + prose block of each element w3c/svgwg#113 (1 comment by @AmeliaBR)
-
Limit pattern & gradient attributes that are inheritable using href w3c/svgwg#121 (1 comment by @AmeliaBR)
-
Define behaviour of `<stop>` if `offset` value not specified. w3c/svgwg#217 (1 comment by @nikosandronikos)
-
Generalizing the utility of refx and refy by using their inverse, dx and dy w3c/svgwg#146 (1 comment by @Tavmjong)
-
Either make mesh a SVGGraphicsElement or make it not render to screen w3c/svgwg#169 (1 comment by @Tavmjong)
-
Define interaction of markerUnits="strokeWidth" and non-scaling-stroke w3c/svgwg#187 (1 comment by @Tavmjong)
-
Specify which attributes/properties are horizontal vs vertical vs other w3c/svgwg#211 (1 comment by @nikosandronikos)
-
Rendering chapter must be more clear about the normative requirements w3c/svgwg#106 (1 comment by @AmeliaBR)
-
Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement w3c/svgwg#60 (1 comment by @AmeliaBR)
-
Add stub pages to SVG 2 for chapters that have been moved to separate specs w3c/svgwg#195 (1 comment by @nikosandronikos)
-
Github issues not being redirected to public-svg-issues mailing list w3c/svgwg#57 (1 comment by @nikosandronikos)
-
Update all the cross-references from SVG 2 to other specs w3c/svgwg#189 (1 comment by @nikosandronikos)
-
-
2 pull requests opened.
-
Use element re-write & related changes w3c/svgwg#206, by @AmeliaBR.
-
implnote.html: fix θ₁ → Δθ w3c/svgwg#202, by @waldyrious.
-
-
2 pull requests merged.
-
Use element re-write & related changes w3c/svgwg#206.
-
implnote.html: fix θ₁ → Δθ w3c/svgwg#202.
-
-
2 pull requests received 28 new comments.
-
Use element re-write & related changes w3c/svgwg#206 (24 comments by @adanilo, @AmeliaBR, @birtles, @nikosandronikos, @Tavmjong)
-
GitHub
w3c/svgwg
-
31 issues opened.
-
Restore SVGSVGElement.prototype.getElementById w3c/svgwg#182, by @foolip.
-
Use a single-case name for meshGradient w3c/svgwg#181, by @AmeliaBR.
-
Use CSS gradient rules for transitioning semi-transparent stop-colors w3c/svgwg#180, by @AmeliaBR.
-
Better error handling for nested links w3c/svgwg#178, by @AmeliaBR.
-
Update default role mapping table to match latest SVG-AAM w3c/svgwg#176, by @AmeliaBR.
-
Make SVGAnimatedX data types extend DOMX data types wherever possible w3c/svgwg#175, by @AmeliaBR.
-
Deprecate <cursor> element w3c/svgwg#174, by @jarek-foksa.
-
Define animatable type for all animatable values w3c/svgwg#173, by @nikosandronikos.
-
Either make mesh a SVGGraphicsElement or make it not render to screen w3c/svgwg#169, by @AmeliaBR.
-
Need to update SVG 2 text layout algorithm w3c/svgwg#166, by @nikosandronikos.
-
<script> and <style> content model should allow only character data. w3c/svgwg#163, by @jarek-foksa.
-
<style> should be allowed everywhere where <script> is allowed w3c/svgwg#162, by @jarek-foksa.
-
SVG element names should not mix camelCase and lowercase notations w3c/svgwg#161, by @jarek-foksa.
-
some remaining preserveAspectRatio="defer" wording needs removing w3c/svgwg#160, by @heycam.
-
Update bounding box algorithm for wrapping text w3c/svgwg#159, by @nikosandronikos.
-
Multi-Page support w3c/svgwg#157, by @eMPee584.
-
Marker section seems to be missing some changes w3c/svgwg#156, by @BigBadaboom.
-
Expose getPathData() on all shapes w3c/svgwg#155, by @jarek-foksa.
-
Shorter equivalent path for the <rect> element w3c/svgwg#154, by @jarek-foksa.
-
Shorter equivalent path for the <circle> element w3c/svgwg#153, by @jarek-foksa.
-
lengthAdjust="spacingAndGlyphs" is a BAD idea w3c/svgwg#152, by @behdad.
-
Update content models with <audio>, <video>, <canvas> and <iframe> w3c/svgwg#151, by @jarek-foksa.
-
Simplify <image> element content model w3c/svgwg#150, by @jarek-foksa.
-
Fix the “the the” typos w3c/svgwg#149, by @prlbr.
-
-
36 issues closed.
-
Note that event names have changed w3c/svgwg#91.
-
Clean up language re <title>/<desc> and tooltips w3c/svgwg#102.
-
Two questions about the `<a>` element w3c/svgwg#26.
-
transformation matrix just specifies 3x3 CTMs w3c/svgwg#3.
-
Initial value for the 'rx' and 'ry' properties w3c/svgwg#74.
-
Shorter equivalent path for the <rect> element w3c/svgwg#154.
-
Define how to interpolate multiple paints in fill and stroke w3c/svgwg#141.
-
Update bounding box algorithm for wrapping text w3c/svgwg#159.
-
Define how meshes are rendered when children of shapes w3c/svgwg#140.
-
Make d a presentation attribute on path w3c/svgwg#119.
-
Simplify <image> element content model w3c/svgwg#150.
-
Full glyph cell term is not defined w3c/svgwg#40.
-
Percentages in 'letter-spacing' and 'word-spacing' w3c/svgwg#143.
-
Request for clarification on complex text shaping w3c/svgwg#65.
-
Marker section seems to be missing some changes w3c/svgwg#156.
-
Shorter equivalent path for the <circle> element w3c/svgwg#153.
-
Add warning to textPath regarding dx/dy/etc w3c/svgwg#124.
-
How should text following <textPath> be positioned? w3c/svgwg#104.
-
Ensure all chapters refer to href and not xlink:href w3c/svgwg#86.
-
Fix the “the the” typos w3c/svgwg#149.
-
-
2 issues reopened.
-
Shorter equivalent path for the <circle> element w3c/svgwg#153, by @jarek-foksa.
-
-
62 issues received 201 new comments.
-
Use CSS gradient rules for transitioning semi-transparent stop-colors w3c/svgwg#180 (13 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos, @SebastianZ, @tabatkins)
-
Allow stroke-dasharray/dashoffset % to be specified relative to path length w3c/svgwg#177 (10 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos, @tabatkins)
-
Marker section seems to be missing some changes w3c/svgwg#156 (10 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos)
-
Restore SVGSVGElement.prototype.getElementById w3c/svgwg#182 (8 comments by @AmeliaBR, @annevk, @erikdahlstrom, @foolip, @nikosandronikos)
-
Shorter equivalent path for the <rect> element w3c/svgwg#154 (8 comments by @AmeliaBR, @BigBadaboom, @jarek-foksa, @nikosandronikos)
-
Clarify whether 'filter' attribute is valid for <tspan> elements w3c/svgwg#103 (8 comments by @AmeliaBR, @nikosandronikos, @Tavmjong)
-
Make unknown elements behave exactly as if the element name were replaced by 'g' w3c/svgwg#122 (8 comments by @AmeliaBR, @erikdahlstrom, @jarek-foksa, @nikosandronikos)
-
Clean up language re <title>/<desc> and tooltips w3c/svgwg#102 (7 comments by @AmeliaBR, @jarek-foksa)
-
Fix switch & conditional processing w3c/svgwg#139 (7 comments by @AmeliaBR, @jarek-foksa, @nikosandronikos, @satakagi)
-
Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element? w3c/svgwg#61 (7 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos, @tabatkins)
-
<script> and <style> content model should allow only character data. w3c/svgwg#163 (7 comments by @AmeliaBR, @jarek-foksa, @nikosandronikos)
-
Simplify <image> element content model w3c/svgwg#150 (6 comments by @AmeliaBR, @jarek-foksa, @nikosandronikos, @prlbr)
-
Better error handling for nested links w3c/svgwg#178 (5 comments by @AmeliaBR, @tabatkins, @Tavmjong)
-
Use a single-case name for meshGradient w3c/svgwg#181 (5 comments by @AmeliaBR, @tabatkins, @Tavmjong)
-
Define how SVG paint server units interact with CSS-inspired fill/stroke sizing properties w3c/svgwg#167 (5 comments by @AmeliaBR, @tabatkins)
-
SVG element names should not mix camelCase and lowercase notations w3c/svgwg#161 (5 comments by @AmeliaBR, @jarek-foksa, @prlbr, @tabatkins)
-
Marker element percentages are missing reference values w3c/svgwg#64 (4 comments by @AmeliaBR, @karip, @nikosandronikos, @Tavmjong)
-
Define behavior of unknown elements inside text & other special constructs w3c/svgwg#179 (3 comments by @AmeliaBR, @BigBadaboom)
-
Define how meshes are rendered when children of shapes w3c/svgwg#140 (3 comments by @AmeliaBR, @jarek-foksa, @tabatkins)
-
<style> should be allowed everywhere where <script> is allowed w3c/svgwg#162 (3 comments by @AmeliaBR, @jarek-foksa)
-
Shorter equivalent path for the <circle> element w3c/svgwg#153 (3 comments by @BigBadaboom, @jarek-foksa, @nikosandronikos)
-
Move path interrogation functions to SVGGeometryElement w3c/svgwg#69 (3 comments by @AmeliaBR, @jarek-foksa)
-
Support SMIL `allowReorder` processing for `systemLanguage` attribute w3c/svgwg#136 (3 comments by @AmeliaBR, @nikosandronikos)
-
Limit pattern & gradient attributes that are inheritable using href w3c/svgwg#121 (2 comments by @AmeliaBR, @nikosandronikos)
-
Shouldn't gradientTransform precede object bounding box to user space conversion? w3c/svgwg#135 (2 comments by @AmeliaBR, @Tavmjong)
-
Spec behavior of ::before and ::after within SVG text w3c/svgwg#125 (2 comments by @tabatkins, @Tavmjong)
-
Error Processing should talk about when to use initial values for attributes w3c/svgwg#52 (2 comments by @nikosandronikos)
-
'auto' value for vertical text when coupled with the obsolete SVG 'gyph-orientation-vertical' is broken w3c/svgwg#33 (2 comments by @nikosandronikos, @Tavmjong)
-
Should SVG keep or drop dominant-baseline values not supported by CSS? w3c/svgwg#31 (2 comments by @nikosandronikos)
-
Parameters and Switch command to allow parametric SVGs w3c/svgwg#128 (2 comments by @Emasoft, @Llbe)
-
Conflict between 'textPath' and 'text-overflow' rules at ends of path. w3c/svgwg#78 (2 comments by @Tavmjong)
-
Update href attribute descriptions to reference HTML51's obtain the resource algorithm w3c/svgwg#90 (1 comment by @karip)
-
Define how to interpolate multiple paints in fill and stroke w3c/svgwg#141 (1 comment by @nikosandronikos)
-
Either make mesh a SVGGraphicsElement or make it not render to screen w3c/svgwg#169 (1 comment by @nikosandronikos)
-
Support CSS images in fill/stroke, and create sub-properties to control sizing w3c/svgwg#168 (1 comment by @AmeliaBR)
-
Can we remove presentation attribute / element table from Attribute Index appendix? w3c/svgwg#83 (1 comment by @nikosandronikos)
-
Multilingual titles and ARIA fallbacks don't work well together w3c/svgwg#116 (1 comment by @AmeliaBR)
-
Define purpose of other namespaced markup in <title> and <desc> w3c/svgwg#101 (1 comment by @jarek-foksa)
-
Support media queries in `switch` / as a conditional processing attribute w3c/svgwg#137 (1 comment by @satakagi)
-
Update content models with <audio>, <video>, <canvas> and <iframe> w3c/svgwg#151 (1 comment by @AmeliaBR)
-
-
3 pull requests opened.
-
Title & desc re-write w3c/svgwg#170, by @AmeliaBR.
-
Note on pattern overflow. w3c/svgwg#164, by @Tavmjong.
-
Revisions to sentence on focusable elements w3c/svgwg#158, by @bpmcneilly.
-
-
2 pull requests merged.
-
Note on pattern overflow. w3c/svgwg#164.
-
Title & desc re-write w3c/svgwg#170.
-
-
1 pull request received 1 new comment.
SVG Accessibility Task Force
GitHub
w3c/aria
-
3 issues opened in the SVG Accessibility Task Force.
-
HTML-AAM: Remove MSAA+UIA Express column w3c/aria#404, by @jasonkiss.
-
describing the relationship between html-aam and core-aam mappings w3c/aria#402, by @jasonkiss.
-
Mac "AX" property and value names in AAM specs w3c/aria#399, by @jasonkiss.
-
-
8 issues closed in the SVG Accessibility Task Force.
-
HTML-AAM Update AX mappings for sub and sup elements w3c/aria#374.
-
HTML-AAM: UIA mapping for <label> w3c/aria#171.
-
CORE-AAM: UIA mapping for status w3c/aria#308.
-
Importing jquery-1.9.0.min.js w3c/aria#394.
-
-
12 issues in the SVG Accessibility Task Force received 34 new comments.
-
Mac "AX" property and value names in AAM specs w3c/aria#399 (19 comments by @cookiecrook, @fredesch, @jasonkiss, @joanmarie)
-
[HTML-AAM] Should refer to HTML spec for defining column and row headers w3c/aria#376 (1 comment by @jasonkiss)
-
HTML-AAM: select element should map to listbox role regardless of presentation w3c/aria#359 (1 comment by @asurkov)
-
HTML-AAM: input element in search state should map to ARIA 1.1 role=searchbox w3c/aria#310 (1 comment by @jasonkiss)
-
SVG-AAM: Issues with the use of title attribute in name and description calculation w3c/aria#137 (1 comment by @fredesch)
-
[SCRIPTS] The <*ref> to <code> magic fails to work in list items w3c/aria#377 (1 comment by @joanmarie)
-
-
6 pull requests opened in the SVG Accessibility Task Force.
-
Action2039 autocomplete w3c/aria#403, by @joanmarie.
-
Added code to accumulate lists of where names are from w3c/aria#401, by @halindrome.
-
Addresses issue with subclass roles being dropped w3c/aria#400, by @halindrome.
-
action 1706 UIA Express w3c/aria#398, by @cyns.
-
action-2065 w3c/aria#397, by @cyns.
-
Add warning about password role w3c/aria#396, by @ZoeBijl.
-
-
6 pull requests merged in the SVG Accessibility Task Force.
-
Action2039 autocomplete w3c/aria#403.
-
Added code to accumulate lists of where names are from w3c/aria#401.
-
Addresses issue with subclass roles being dropped w3c/aria#400.
-
Added detection of required states or properties. w3c/aria#395.
-
Add warning about password role w3c/aria#396.
-
Gm intro w3c/aria#385.
-
-
2 pull requests closed in the SVG Accessibility Task Force.
-
action-2065 w3c/aria#397.
-
action 1706 UIA Express w3c/aria#398.
-
-
6 pull requests in the SVG Accessibility Task Force received 17 new comments.
-
Added code to accumulate lists of where names are from w3c/aria#401 (7 comments by @halindrome, @joanmarie)
-
Added detection of required states or properties. w3c/aria#395 (5 comments by @halindrome, @joanmarie)
-
GitHub
w3c/svgwg
-
17 issues opened.
-
SVG Paths spec vs Paths chapter of SVG2 w3c/svgwg#148, by @SimonSapin.
-
Independent stroke width for sub-paths w3c/svgwg#147, by @nikosandronikos.
-
Clarify SVG Integration spec re expectations for SVG in OpenType w3c/svgwg#145, by @AmeliaBR.
-
Unit of numbers in path data w3c/svgwg#144, by @SimonSapin.
-
Percentages in 'letter-spacing' and 'word-spacing' w3c/svgwg#143, by @Tavmjong.
-
Define how to interpolate multiple paints in fill and stroke w3c/svgwg#141, by @karip.
-
Define how meshes are rendered when children of shapes w3c/svgwg#140, by @karip.
-
Fix switch & conditional processing w3c/svgwg#139, by @AmeliaBR.
-
Define how `requiredExtensions` values should be interpreted w3c/svgwg#138, by @AmeliaBR.
-
Support SMIL `allowReorder` processing for `systemLanguage` attribute w3c/svgwg#136, by @AmeliaBR.
-
SVG Integration Spec should define when audio/video is played w3c/svgwg#131, by @karip.
-
Add a way to specify a ping-pong animation in SVG w3c/svgwg#130, by @Emasoft.
-
Define overflow:visible behavior for pattern tiles w3c/svgwg#129, by @AmeliaBR.
-
-
10 issues closed.
-
Unit of numbers in path data w3c/svgwg#144.
-
Direction of markers and line caps on segment boundaries w3c/svgwg#79.
-
Support scoped attribute on style element w3c/svgwg#118.
-
Result for a value of zero for pathLength is undefined w3c/svgwg#81.
-
Rename the d attribute on textPath to 'path' w3c/svgwg#120.
-
-
1 issue reopened.
-
Add a way to specify a ping-pong animation in SVG w3c/svgwg#130, by @AmeliaBR.
-
-
21 issues received 55 new comments.
-
Define overflow:visible behavior for pattern tiles w3c/svgwg#129 (11 comments by @AmeliaBR, @BigBadaboom, @dennisgaebel, @Emasoft, @heycam, @nikosandronikos, @Tavmjong)
-
closepath behaviour when filling in missing points needs some improvement w3c/svgwg#126 (10 comments by @AmeliaBR, @nikosandronikos)
-
Add a way to specify a ping-pong animation in SVG w3c/svgwg#130 (7 comments by @AmeliaBR, @Emasoft, @tabatkins)
-
SVG Integration Spec should define when audio/video is played w3c/svgwg#131 (4 comments by @badcat, @Emasoft, @karip)
-
Clarify what is the size of a use element if width and height are not specified w3c/svgwg#142 (3 comments by @AmeliaBR, @BigBadaboom, @karip)
-
Clean up language re <title>/<desc> and tooltips w3c/svgwg#102 (2 comments by @AmeliaBR, @nikosandronikos)
-
Define how to interpolate multiple paints in fill and stroke w3c/svgwg#141 (2 comments by @AmeliaBR, @tabatkins)
-
Define how meshes are rendered when children of shapes w3c/svgwg#140 (2 comments by @AmeliaBR, @karip)
-
Direction of markers and line caps on segment boundaries w3c/svgwg#79 (1 comment by @nikosandronikos)
-
Update grammar for path data to reflect changes to closepath command w3c/svgwg#89 (1 comment by @nikosandronikos)
-
Can we re-define attribute values to use ABNF or EBNF, not a mix of both? w3c/svgwg#108 (1 comment by @nikosandronikos)
-
Define purpose of other namespaced markup in <title> and <desc> w3c/svgwg#101 (1 comment by @nikosandronikos)
-
Shouldn't gradientTransform precede object bounding box to user space conversion? w3c/svgwg#135 (1 comment by @andrei-datcu)
-
Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element? w3c/svgwg#61 (1 comment by @etlovett)
-
-
3 pull requests opened.
-
adding example files for SVG Authoring w3c/svgwg#134, by @shepazu.
-
first draft from file w3c/svgwg#133, by @shepazu.
-
first draft from file w3c/svgwg#132, by @shepazu.
-
-
3 pull requests merged.
-
adding example files for SVG Authoring w3c/svgwg#134.
-
first draft from file w3c/svgwg#133.
-
first draft from file w3c/svgwg#132.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
21 issues opened in the SVG Accessibility Task Force.
-
Importing jquery-1.9.0.min.js w3c/aria#394, by @marcoscaceres.
-
Biblio.js contains SpecRef dups w3c/aria#391, by @marcoscaceres.
-
CSS AAM: docs with layout/read order issues w3c/aria#383, by @fredesch.
-
HTML-AAM: how to treat <img alt> with no value w3c/aria#381, by @cyns.
-
HTML-AAM: "img (alt attribute is empty)" reword for clarity w3c/aria#380, by @cyns.
-
[SCRIPTS] The <*ref> to <code> magic fails to work in list items w3c/aria#377, by @joanmarie.
-
HTML-AAM check AX role mappings against webkit expected w3c/aria#375, by @stevefaulkner.
-
HTML-AAM Update AX mappings for sub and sup elements w3c/aria#374, by @stevefaulkner.
-
<dl> role should = list w3c/aria#371, by @stevefaulkner.
-
html-aam: name calculation doesn't seem to cover embedded controls w3c/aria#369, by @cyns.
-
HTML-AAM: determine right mappings for popup ui for input type=color w3c/aria#363, by @cyns.
-
-
5 issues closed in the SVG Accessibility Task Force.
-
HTML-AAM: suggestion: add "see also NAME-AAM" to @label w3c/aria#189.
-
21 issues in the SVG Accessibility Task Force received 33 new comments.
-
HTML-AAM: should aria-placeholder be used for accessible description on elements? w3c/aria#334 (6 comments by @AmeliaBR, @cyns, @dstorey, @jasonkiss)
-
[SCRIPTS] Subclass roles missing from ARIA properties tables after 0460074 w3c/aria#382 (4 comments by @halindrome, @joanmarie)
-
HTML-AAM: determine right mappings for browser generated form validation error messages w3c/aria#360 (2 comments by @cyns)
-
[SCRIPTS] Add (or restore/fix) programmatic way to mark required inherited properties w3c/aria#386 (1 comment by @halindrome)
-
HTML Accessibility API doesn't specific how accessible name calculation is applied to iframes w3c/aria#274 (1 comment by @jasonkiss)
-
html-aam: output element should take name from contents, have its own section w3c/aria#368 (1 comment by @jasonkiss)
-
html-aam: generic text elements should take name from contents, be consistant with accname-aam w3c/aria#367 (1 comment by @jasonkiss)
-
HTML-AAM: Make presentation of UIA mapping properties consistent w3c/aria#252 (1 comment by @jasonkiss)
-
SVG-AAM: Consider explicit language regarding inclusion of elements with child title or desc w3c/aria#134 (1 comment by @AmeliaBR)
-
SVG-AAM: Issues with the use of title attribute in name and description calculation w3c/aria#137 (1 comment by @AmeliaBR)
-
html-aam: name calculation doesn't seem to cover embedded controls w3c/aria#369 (1 comment by @cyns)
-
HTML-AAM: determine right mappings for popup ui for input type=color w3c/aria#363 (1 comment by @cyns)
-
HTML-AAM: determine right mappings for popup ui for date and time inputs w3c/aria#364 (1 comment by @cyns)
-
HTML-AAM: determine right UIA mapping for browser generated form validation error messages w3c/aria#160 (1 comment by @cyns)
-
[graphics][svg-aam][graphics-aam] Change graphics-doc to graphics-document w3c/aria#356 (1 comment by @AmeliaBR)
-
-
17 pull requests opened in the SVG Accessibility Task Force.
-
Added detection of required states or properties. w3c/aria#395, by @halindrome.
-
Remove redudant jQuery w3c/aria#393, by @marcoscaceres.
-
Remove redudant jQuery w3c/aria#392, by @marcoscaceres.
-
AXAPI aready in SpecRef w3c/aria#390, by @marcoscaceres.
-
ATK is in SpecRef w3c/aria#389, by @marcoscaceres.
-
ARIA-PRACTICES in SpecRef w3c/aria#388, by @marcoscaceres.
-
Updated to use require to load respec pieces w3c/aria#387, by @halindrome.
-
Added introduction to Graphics AAM w3c/aria#384, by @fredesch.
-
Shane 377 w3c/aria#379, by @halindrome.
-
Change to support heading level suppression w3c/aria#378, by @halindrome.
-
SVG-AAM: Use graphics roles, fix unclear requirements w3c/aria#373, by @AmeliaBR.
-
Accname update w3c/aria#370, by @cyns.
-
Remove redundant sentence from paragraph w3c/aria#366, by @carmacleod.
-
Graphics roles editorial changes w3c/aria#365, by @AmeliaBR.
-
Updated handling of rdef, pdef, and sdef elements w3c/aria#361, by @halindrome.
-
Updated aria examples, banner and contenting w3c/aria#358, by @jongund.
-
-
7 pull requests merged in the SVG Accessibility Task Force.
-
Updated to use require to load respec pieces w3c/aria#387.
-
SVG-AAM: Use graphics roles, fix unclear requirements w3c/aria#373.
-
Accname update w3c/aria#370.
-
Change to support heading level suppression w3c/aria#378.
-
Shane 377 w3c/aria#379.
-
Updated handling of rdef, pdef, and sdef elements w3c/aria#361.
-
Graphics roles editorial changes w3c/aria#365.
-
-
2 pull requests closed in the SVG Accessibility Task Force.
-
Added introduction to Graphics AAM w3c/aria#384.
-
Removing "golden hammer" language w3c/aria#354.
-
-
8 pull requests in the SVG Accessibility Task Force received 14 new comments.
-
Added detection of required states or properties. w3c/aria#395 (3 comments by @halindrome, @joanmarie)
-
Participants
-
1 organization joined.
-
Canon, Inc. joined.
-
-
1 organization left.
-
Canon, Inc. left.
-
GitHub
w3c/svgwg
-
51 issues opened.
-
Parameters and Switch command to allow parametric SVGs w3c/svgwg#128, by @Emasoft.
-
Spec behavior of ::before and ::after within SVG text w3c/svgwg#125, by @AmeliaBR.
-
Add warning to textPath regarding dx/dy/etc w3c/svgwg#124, by @AmeliaBR.
-
Add definitions of "open path" and "closed path" to path chapter w3c/svgwg#123, by @AmeliaBR.
-
Limit pattern & gradient attributes that are inheritable using href w3c/svgwg#121, by @jarek-foksa.
-
Rename the d attribute on textPath to 'path' w3c/svgwg#120, by @nikosandronikos.
-
Make d a presentation attribute on path w3c/svgwg#119, by @nikosandronikos.
-
Support scoped attribute on style element w3c/svgwg#118, by @nikosandronikos.
-
Multilingual titles and ARIA fallbacks don't work well together w3c/svgwg#116, by @chaals.
-
Rewrite all element descriptions to use normative language w3c/svgwg#111, by @AmeliaBR.
-
replace IEEE definition of single precision float w3c/svgwg#109, by @chaals.
-
Keep xlink:href in examples linked to in spec. w3c/svgwg#105, by @Tavmjong.
-
How should text following <textPath> be positioned? w3c/svgwg#104, by @progers.
-
Clarify whether 'filter' attribute is valid for <tspan> elements w3c/svgwg#103, by @BigBadaboom.
-
Clean up language re <title>/<desc> and tooltips w3c/svgwg#102, by @nikosandronikos.
-
Define purpose of other namespaced markup in <title> and <desc> w3c/svgwg#101, by @nikosandronikos.
-
Should SVGUnknownElement be a container element? w3c/svgwg#97, by @nikosandronikos.
-
Review content model and allowed attributes on all elements w3c/svgwg#93, by @nikosandronikos.
-
Add more modern event handling examples w3c/svgwg#92, by @nikosandronikos.
-
Note that event names have changed w3c/svgwg#91, by @nikosandronikos.
-
Ensure all chapters refer to href and not xlink:href w3c/svgwg#86, by @nikosandronikos.
-
Property index (appendix) needs updating w3c/svgwg#82, by @nikosandronikos.
-
Result for a value of zero for pathLength is undefined w3c/svgwg#81, by @nikosandronikos.
-
'kerning' property in SVG 2 w3c/svgwg#80, by @Tavmjong.
-
Direction of markers and line caps on segment boundaries w3c/svgwg#79, by @nikosandronikos.
-
Remove any mention of "outline of canvas" w3c/svgwg#77, by @jarek-foksa.
-
Add getScreenBBox() method to SVGGraphicsElement interface w3c/svgwg#76, by @jarek-foksa.
-
-
21 issues closed.
-
replace IEEE definition of single precision float w3c/svgwg#109.
-
Where to position the first line of text in a shape? w3c/svgwg#35.
-
Should SVGUnknownElement be a container element? w3c/svgwg#97.
-
How should degenerate closed paths render in SVG ? w3c/svgwg#42.
-
Move path interrogation functions to SVGGeometryElement w3c/svgwg#69.
-
Remove any mention of "outline of canvas" w3c/svgwg#77.
-
Clean-up broken links to HTML 5.1 w3c/svgwg#66.
-
'kerning' property in SVG 2 w3c/svgwg#80.
-
How to fill text sequentially into multiple shapes? w3c/svgwg#38.
-
How to handle overflow for text in a shape? w3c/svgwg#36.
-
How does SVG text interact with CSS? w3c/svgwg#30.
-
How is the first glyph positioned in a line? w3c/svgwg#39.
-
How does wrap-flow apply when a shape has holes? w3c/svgwg#37.
-
-
1 issue reopened.
-
Initial value for the 'rx' and 'ry' properties w3c/svgwg#74, by @AmeliaBR.
-
-
41 issues received 93 new comments.
-
Request for clarification on complex text shaping w3c/svgwg#65 (11 comments by @AmeliaBR, @heycam, @progers, @Tavmjong)
-
Clarify whether 'filter' attribute is valid for <tspan> elements w3c/svgwg#103 (7 comments by @AmeliaBR, @BigBadaboom, @fsoder)
-
How should text following <textPath> be positioned? w3c/svgwg#104 (5 comments by @AmeliaBR, @BigBadaboom, @fsoder, @nikosandronikos)
-
Result for a value of zero for pathLength is undefined w3c/svgwg#81 (5 comments by @AmeliaBR, @BigBadaboom, @fsoder, @nikosandronikos)
-
Initial value for the 'rx' and 'ry' properties w3c/svgwg#74 (5 comments by @AmeliaBR, @BigBadaboom, @fsoder)
-
Make unknown elements behave exactly as if the element name were replaced by 'g' w3c/svgwg#122 (4 comments by @dirkschulze, @nikosandronikos)
-
Conflict between 'textPath' and 'text-overflow' rules at ends of path. w3c/svgwg#78 (4 comments by @heycam, @Tavmjong)
-
Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element? w3c/svgwg#61 (3 comments by @fsoder, @nikosandronikos, @tabatkins)
-
Spec behavior of ::before and ::after within SVG text w3c/svgwg#125 (3 comments by @AmeliaBR, @tabatkins)
-
Rendering chapter must be more clear about the normative requirements w3c/svgwg#106 (3 comments by @chaals, @nikosandronikos)
-
transformation matrix just specifies 3x3 CTMs w3c/svgwg#3 (2 comments by @dirkschulze, @nikosandronikos)
-
Limit pattern & gradient attributes that are inheritable using href w3c/svgwg#121 (2 comments by @AmeliaBR, @nikosandronikos)
-
Clean up language re <title>/<desc> and tooltips w3c/svgwg#102 (2 comments by @AmeliaBR, @nikosandronikos)
-
Rewrite <title> and <desc> description in light of accessibility changes w3c/svgwg#100 (2 comments by @nikosandronikos)
-
window.SVGDocument alias is probably not needed for web compat w3c/svgwg#18 (1 comment by @nikosandronikos)
-
Multilingual titles and ARIA fallbacks don't work well together w3c/svgwg#116 (1 comment by @chaals)
-
We should define the behavior of ‘use’ in terms of Web Components w3c/svgwg#99 (1 comment by @AmeliaBR)
-
Direction of markers and line caps on segment boundaries w3c/svgwg#79 (1 comment by @nikosandronikos)
-
Do we need to mention anything about attributes, properties and such on SVGUnknownElements? w3c/svgwg#96 (1 comment by @nikosandronikos)
-
Should it be possible to somehow force rendering of unknown elements in other namespaces? w3c/svgwg#95 (1 comment by @nikosandronikos)
-
Fix stylesheet so that element names aren't in the top right corner of the element definition table w3c/svgwg#112 (1 comment by @nikosandronikos)
-
Define purpose of other namespaced markup in <title> and <desc> w3c/svgwg#101 (1 comment by @nikosandronikos)
-
Move path interrogation functions to SVGGeometryElement w3c/svgwg#69 (1 comment by @nikosandronikos)
-
Develop a new standard for describing "layers" in SVG authoring tools w3c/svgwg#68 (1 comment by @Tavmjong)
-
-
2 pull requests opened.
-
tighten desc/title, note localisation at risk w3c/svgwg#114, by @chaals.
-
2 pull requests merged.
-
Master w3c/svgwg#115.
-
tighten desc/title, note localisation at risk w3c/svgwg#114.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
30 issues opened in the SVG Accessibility Task Force.
-
accname-aam: step 2E, rule for button can cause infinite loop w3c/aria#357, by @cyns.
-
ARIA 1.1: Label navigation landmarks if more than one per page w3c/aria#355, by @carmacleod.
-
HTML-AAM: td and tr Name and Description Computation not specified w3c/aria#352, by @cyns.
-
ARIA 1.1: Feed supports aria-setsize w3c/aria#351, by @carmacleod.
-
Landmarks - Assistive technologies SHOULD; user agents MAY... w3c/aria#350, by @carmacleod.
-
[APG] pattern-combobox w3c/aria#349, by @jnurthen.
-
[HTML-AAM] SVG element should be role=graphics-document w3c/aria#347, by @stevefaulkner.
-
HTML-AAM: UIA mapping for output element w3c/aria#345, by @cyns.
-
HTML-AAM: possible aria mapping for meter w3c/aria#344, by @cyns.
-
HTML-AAM: UIA mapping for placeholder w3c/aria#340, by @cyns.
-
WAI-ARIA 1.1: Editorial comments for Sections 3 and 4 w3c/aria#333, by @carmacleod.
-
WAI-ARIA 1.1: Missing Tables in Appendix D w3c/aria#331, by @carmacleod.
-
WAI-ARIA 1.1: Editorial comments for Sections 1 and 2 w3c/aria#329, by @carmacleod.
-
WAI-ARIA 1.1: Update Authoring Practices links to 1.1 ? w3c/aria#328, by @carmacleod.
-
HTML-AAM: should meter be focusable? w3c/aria#327, by @cyns.
-
Missing disclosure design pattern w3c/aria#326, by @ZoeBijl.
-
CORE-AAM: UIA mapping for Link role should have value pattern w3c/aria#325, by @cyns.
-
HTML-AAM: video should have UIA localized control type w3c/aria#324, by @cyns.
-
2.13 Grid (Simple Data Tables) - changes w3c/aria#323, by @jnurthen.
-
WAI-ARIA 1.1: about XML w3c/aria#321, by @momdo.
-
WAI-ARIA 1.1: Needs to update link to SIML w3c/aria#320, by @momdo.
-
-
37 issues closed in the SVG Accessibility Task Force.
-
[APG] pattern-combobox w3c/aria#349.
-
Missing disclosure design pattern w3c/aria#326.
-
2.13 Grid (Simple Data Tables) - changes w3c/aria#323.
-
Remove title attribute from code example links w3c/aria#299.
-
APG missing media player section w3c/aria#293.
-
[practices WD] math w3c/aria#290.
-
Rename tab panel design pattern w3c/aria#286.
-
retire - put health warning on WAI-ARIA Primer 1.0 w3c/aria#249.
-
Definition of Internationalizable w3c/aria#226.
-
Should tab panels activate on focus? w3c/aria#206.
-
Create tab panel code example w3c/aria#204.
-
APG: Add bread crumb design pattern w3c/aria#130.
-
aria-expanded is unclear w3c/aria#115.
-
Tab Panel keyboard interaction w3c/aria#113.
-
Code standard w3c/aria#95.
-
APG: Need for an abstract page description w3c/aria#78.
-
Add progressive disclosure design pattern w3c/aria#61.
-
APG guidance for touch devices w3c/aria#60.
-
Header element semantics w3c/aria#276.
-
Needs mappings for datetime-local w3c/aria#248.
-
ARIA 1.1: Feed supports aria-setsize w3c/aria#351.
-
HTML-AAM: video should have UIA localized control type w3c/aria#324.
-
HTML-AAM: UIA mapping for output element w3c/aria#345.
-
HTML-AAM: UIA mapping for <time> element w3c/aria#235.
-
WAI-ARIA 1.1: Editorial comments for Sections 3 and 4 w3c/aria#333.
-
min-width on table headings causes issues w3c/aria#302.
-
-
1 issue reopened in the SVG Accessibility Task Force.
-
[HTML-AAM] SVG element should be role=graphics-document w3c/aria#347, by @fredesch.
-
-
46 issues in the SVG Accessibility Task Force received 86 new comments.
-
[HTML-AAM] SVG element should be role=graphics-document w3c/aria#347 (16 comments by @AmeliaBR, @cookiecrook, @fredesch, @joanmarie, @LJWatson, @richschwer)
-
HTML-AAM: should aria-placeholder be used for accessible description on elements? w3c/aria#334 (5 comments by @cyns, @stevefaulkner)
-
Enforce beautify standards and validate code to catch mistakes w3c/aria#202 (3 comments by @handcoding, @ZoeBijl)
-
HTML-AAM: 5.12 name/description calculation for Section and Grouping elements overrides accname-aam w3c/aria#336 (3 comments by @cyns, @klown)
-
ARIA 1.1: Label navigation landmarks if more than one per page w3c/aria#355 (2 comments by @carmacleod, @jnurthen)
-
WAI-ARIA 1.1: Editorial comments for Sections 3 and 4 w3c/aria#333 (2 comments by @carmacleod, @joanmarie)
-
HTML-AAM: no mention of aria-placeholder in name/description calculation w3c/aria#338 (2 comments by @cyns)
-
WAI-ARIA Authoring Practices <h1> recommendation doesn't match HTML 5.1 spec w3c/aria#127 (1 comment by @ZoeBijl)
-
The seciton about role=menubar should caution authors not to use it for navigation menus w3c/aria#102 (1 comment by @ZoeBijl)
-
w3c/aria#95 (1 comment by @ZoeBijl)
-
w3c/aria#88 (1 comment by @ZoeBijl)
-
w3c/aria#78 (1 comment by @ZoeBijl)
-
w3c/aria#61 (1 comment by @ZoeBijl)
-
w3c/aria#60 (1 comment by @ZoeBijl)
-
HTML-AAM: change UIA mapping for @required to "use wai-aria mapping" w3c/aria#316 (1 comment by @jasonkiss)
-
HTML-AAM: add "text alternative" definition from accname-aam to name and description section w3c/aria#306 (1 comment by @jasonkiss)
-
HTML-AAM: (editorial) mark element UIA mapping has too much code styling w3c/aria#269 (1 comment by @jasonkiss)
-
HTML-AAM: <footer> that is not child of body should not be group in UIA w3c/aria#151 (1 comment by @jasonkiss)
-
HTML-AAM: td and tr Name and Description Computation not specified w3c/aria#352 (1 comment by @AmeliaBR)
-
-
10 pull requests opened in the SVG Accessibility Task Force.
-
Removing "golden hammer" language w3c/aria#354, by @bpmcneilly.
-
Uia updates w3c/aria#346, by @cyns.
-
inconsistent pluralization in new landmarks section w3c/aria#341, by @carmacleod.
-
Add Landmarks Section based on 4/18/2016 meeting. w3c/aria#335, by @jnurthen.
-
Changed references to authoring practices to 1.1 version w3c/aria#332, by @jnurthen.
-
A11ydoer-patch- menubuttonexlink w3c/aria#319, by @a11ydoer.
-
Replace tables in design patterns with headings w3c/aria#318, by @ZoeBijl.
-
Replace tables in design patterns with headings w3c/aria#317, by @ZoeBijl.
-
-
9 pull requests merged in the SVG Accessibility Task Force.
-
Uia updates w3c/aria#346.
-
Changed references to authoring practices to 1.1 version w3c/aria#332.
-
inconsistent pluralization in new landmarks section w3c/aria#341.
-
Add Landmarks Section based on 4/18/2016 meeting. w3c/aria#335.
-
Mcpubfixes w3c/aria#301.
-
Replace tables in design patterns with headings w3c/aria#318.
-
Action 2008 w3c/aria#313.
-
5 pull requests closed in the SVG Accessibility Task Force.
-
A11ydoer-patch- menubuttonexlink w3c/aria#319.
-
adding menu button example file w3c/aria#298.
-
fix link to menu button example w3c/aria#297.
-
Replace tables in design patterns with headings w3c/aria#317.
-
9 pull requests in the SVG Accessibility Task Force received 18 new comments.
-
Changed references to authoring practices to 1.1 version w3c/aria#332 (3 comments by @jnurthen, @ZoeBijl)
-
Updated examples including menu button 1 and Landmark section of authoring practices w3c/aria#288 (2 comments by @jnurthen, @jongund)
-
Move scrollbar role section to correct position in alphabetical order… w3c/aria#348 (1 comment by @joanmarie)
-
minor typos and missing words. feed was missing its [ARIA 1.1] marker. w3c/aria#342 (1 comment by @joanmarie)
SVG Accessibility Task Force
GitHub
w3c/aria
-
24 issues opened in the SVG Accessibility Task Force.
-
HTML-AAM: change UIA mapping for @required to "use wai-aria mapping" w3c/aria#316, by @cyns.
-
HTML-AAM: aria mapping for @hidden is blank w3c/aria#315, by @cyns.
-
HTML-AAM: UIA mapping for time element w3c/aria#314, by @cyns.
-
Typo "this criteria" w3c/aria#311, by @mitchellevan.
-
HTML-AAM: role=status is not a good match for output element w3c/aria#309, by @cyns.
-
CORE-AAM: UIA mapping for status w3c/aria#308, by @cyns.
-
min-width on table headings causes issues w3c/aria#302, by @ZoeBijl.
-
Remove title attribute from code example links w3c/aria#299, by @ZoeBijl.
-
APG missing media player section w3c/aria#293, by @jnurthen.
-
[practices WD] math w3c/aria#290, by @pkra.
-
Rename tab panel design pattern w3c/aria#286, by @ZoeBijl.
-
Suggest attribute name change for aria-kbdshortcuts w3c/aria#285, by @LJWatson.
-
Definition for aria-kbdshortcuts references old specification w3c/aria#284, by @LJWatson.
-
aria-sort should be allowed on multiple columns w3c/aria#283, by @jnurthen.
-
[CORE-AAM] application no longer a landmark w3c/aria#281, by @stevefaulkner.
-
[DPub] Possible issues with role superclasses w3c/aria#278, by @joanmarie.
-
[HTML-AAM] proscribe header/footer mappings to landmark roles w3c/aria#277, by @stevefaulkner.
-
Header element semantics w3c/aria#276, by @jongund.
-
article role/HTML5 element semantics w3c/aria#275, by @stevefaulkner.
-
-
5 issues closed in the SVG Accessibility Task Force.
-
Typo "this criteria" w3c/aria#311.
-
[DPub] Possible issues with role superclasses w3c/aria#278.
-
Practices: ALT+del conflicts with JAWS keystroke w3c/aria#1.
-
24 issues in the SVG Accessibility Task Force received 69 new comments.
-
[HTML-AAM] proscribe header/footer mappings to landmark roles w3c/aria#277 (23 comments by @jasonkiss, @jongund, @LJWatson, @MarcoZehe, @stevefaulkner, @ZoeBijl)
-
[CORE-AAM] application no longer a landmark w3c/aria#281 (5 comments by @cookiecrook, @klown, @stevefaulkner)
-
SVG-AAM / Core AAM: Consider explicit language regarding objects with presentational role and ARIA attributes w3c/aria#136 (4 comments by @AmeliaBR)
-
HTML-AAM: role=status is not a good match for output element w3c/aria#309 (3 comments by @cookiecrook, @cyns, @stevefaulkner)
-
HTML-AAM: @abbr should be part of name calculation w3c/aria#181 (3 comments by @jasonkiss, @jnurthen)
-
[DPub] Possible issues with role superclasses w3c/aria#278 (3 comments by @joanmarie, @mattgarrish, @TzviyaSiegman)
-
HTML-AAM: input element in search state should map to ARIA 1.1 role=searchbox w3c/aria#310 (1 comment by @dstorey)
-
Example letters are inconsistent: aria-practices, Widgets within Widgets w3c/aria#312 (1 comment by @jnurthen)
-
HTML Accessibility API doesn't specific how accessible name calculation is applied to iframes w3c/aria#274 (1 comment by @cyns)
-
HTML-AAM: suggestion: add "see also NAME-AAM" to image alt is empty w3c/aria#157 (1 comment by @jasonkiss)
-
HTML-AAM: <footer> that is not child of body should not be group in UIA w3c/aria#151 (1 comment by @jasonkiss)
-
-
18 pull requests opened in the SVG Accessibility Task Force.
-
Action 2008 w3c/aria#313, by @cyns.
-
added UIA FullDescription w3c/aria#305, by @cyns.
-
Action 2032 w3c/aria#304, by @cyns.
-
Mcpubfixes w3c/aria#301, by @michael-n-cooper.
-
Fixed some formatting errors w3c/aria#300, by @halindrome.
-
adding menu button example file w3c/aria#298, by @a11ydoer.
-
fix link to menu button example w3c/aria#297, by @a11ydoer.
-
corrected linked css, js file name w3c/aria#295, by @a11ydoer.
-
corrected linked css, js file name w3c/aria#294, by @a11ydoer.
-
Treeview Changes & Nuke Drag and Drop w3c/aria#292, by @jnurthen.
-
Fixed a typo in Rich Text Editor example. w3c/aria#291, by @mlewand.
-
"accessible" -> "accessible object" where appropriate w3c/aria#289, by @jasonkiss.
-
tab pattern changes - bug 28993 w3c/aria#287, by @jnurthen.
-
Connected to working version of ReSpec. w3c/aria#282, by @halindrome.
-
issues 192 and 154 w3c/aria#280, by @cyns.
-
second round of changes re ACTION-1569 w3c/aria#279, by @jasonkiss.
-
-
10 pull requests merged in the SVG Accessibility Task Force.
-
Action 2032 w3c/aria#304.
-
Fixed some formatting errors w3c/aria#300.
-
Treeview Changes & Nuke Drag and Drop w3c/aria#292.
-
Fixed a typo in Rich Text Editor example. w3c/aria#291.
-
second round of changes re ACTION-1569 w3c/aria#279.
-
tab pattern changes - bug 28993 w3c/aria#287.
-
updates to UIA mappings for ARIA landmark roles w3c/aria#272.
-
Connected to working version of ReSpec. w3c/aria#282.
-
issues 192 and 154 w3c/aria#280.
-
ReSpec event handler to fix scrolling when loading. w3c/aria#256.
-
-
4 pull requests closed in the SVG Accessibility Task Force.
-
added UIA FullDescription w3c/aria#305.
-
corrected linked css, js file name w3c/aria#295.
-
corrected linked css, js file name w3c/aria#294.
-
Jemma w3c/aria#296.
-
-
10 pull requests in the SVG Accessibility Task Force received 29 new comments.
Participants
-
2 organizations joined.
-
Boeing Company joined.
-
Level Access joined.
-
GitHub
w3c/svgwg
-
20 issues opened.
-
XSS Security concerns prevent CSS to be used in SVG animated images w3c/svgwg#75, by @Emasoft.
-
Initial value for the 'rx' and 'ry' properties w3c/svgwg#74, by @fsoder.
-
Should SVG 2 switch to Bikeshed? w3c/svgwg#73, by @nikosandronikos.
-
Syntax to support units & calculations in path data strings w3c/svgwg#72, by @AmeliaBR.
-
SVG 2 has un-used references w3c/svgwg#71, by @nikosandronikos.
-
INTRODUCE A NEW ENTITY CALLED "SET" w3c/svgwg#70, by @Emasoft.
-
Move path interrogation functions to SVGGeometryElement w3c/svgwg#69, by @BigBadaboom.
-
Clean-up broken links to HTML 5.1 w3c/svgwg#66, by @AmeliaBR.
-
Request for clarification on complex text shaping w3c/svgwg#65, by @progers.
-
Marker element percentages are missing reference values w3c/svgwg#64, by @karip.
-
Continue to improve SMIL as the main animation method of SVG w3c/svgwg#63, by @Emasoft.
-
Add layers blending effects in SVG for photoshop compatibility w3c/svgwg#62, by @Emasoft.
-
Support textPath geometry via CSS w3c/svgwg#59, by @AmeliaBR.
-
Decide what to do with zoom and pan w3c/svgwg#56, by @AmeliaBR.
-
-
8 issues closed.
-
INTRODUCE A NEW ENTITY CALLED "SET" w3c/svgwg#70.
-
2 issues reopened.
-
26 issues received 202 new comments.
-
Develop a new standard for describing "layers" in SVG authoring tools w3c/svgwg#68 (40 comments by @AmeliaBR, @BigBadaboom, @Emasoft, @jarek-foksa, @nikosandronikos, @tabatkins)
-
Continue to improve SMIL as the main animation method of SVG w3c/svgwg#63 (39 comments by @AmeliaBR, @birtles, @Emasoft, @nikosandronikos, @progers, @stevenvachon, @tabatkins)
-
Add layers blending effects in SVG for photoshop compatibility w3c/svgwg#62 (36 comments by @AmeliaBR, @BigBadaboom, @Emasoft, @jarek-foksa, @liamquin, @nikosandronikos, @progers, @tabatkins)
-
Move path interrogation functions to SVGGeometryElement w3c/svgwg#69 (13 comments by @AmeliaBR, @jarek-foksa, @nikosandronikos, @progers, @shepazu, @tabatkins)
-
`d` geometric property needs a clear & extensible name w3c/svgwg#49 (13 comments by @AmeliaBR, @BigBadaboom, @nikosandronikos, @prlbr, @progers, @tabatkins)
-
INTRODUCE A NEW ENTITY CALLED "SET" w3c/svgwg#70 (10 comments by @AmeliaBR, @Emasoft, @progers, @tabatkins)
-
Allow filter area (height, width, y, x, filterRes attributes) to be calculated automatically w3c/svgwg#67 (8 comments by @AmeliaBR, @BigBadaboom, @Emasoft, @jarek-foksa)
-
Allow multiple radii for rx & ry in <rect> as per CSS border-radius w3c/svgwg#58 (7 comments by @AmeliaBR, @BigBadaboom, @jarek-foksa, @karip, @progers, @tabatkins)
-
Request for clarification on complex text shaping w3c/svgwg#65 (4 comments by @fsoder, @progers, @Tavmjong)
-
Syntax to support units & calculations in path data strings w3c/svgwg#72 (4 comments by @AmeliaBR, @jarek-foksa, @tabatkins)
-
Directly referencing the HTML Sequential focus navigation and tabindex w3c/svgwg#50 (2 comments by @AmeliaBR)
-
Github issues not being redirected to public-svg-issues mailing list w3c/svgwg#57 (2 comments by @AmeliaBR, @nikosandronikos)
-
XSS Security concerns prevent CSS to be used in SVG animated images w3c/svgwg#75 (1 comment by @tabatkins)
-
should UA style sheet have a rule for visited link color? w3c/svgwg#47 (1 comment by @nikosandronikos)
-
window.SVGDocument alias is probably not needed for web compat w3c/svgwg#18 (1 comment by @nikosandronikos)
-
Adding default values for hanging and mathematical baselines w3c/svgwg#34 (1 comment by @nikosandronikos)
-
Clarify behaviour of baseline tables when changing font size w3c/svgwg#32 (1 comment by @nikosandronikos)
-
Should SVG keep or drop dominant-baseline values not supported by CSS? w3c/svgwg#31 (1 comment by @nikosandronikos)
-
Error Processing should talk about when to use initial values for attributes w3c/svgwg#52 (1 comment by @philiptaylor)
-
-
1 pull request opened.
-
1 pull request merged.
SVG Accessibility Task Force
GitHub
w3c/aria
-
22 issues opened in the SVG Accessibility Task Force.
-
HTML-AAM: should address be treated as seciton/landmark in AAPIs? w3c/aria#273, by @cyns.
-
HTML-AAM: UIA mapping for address w3c/aria#270, by @cyns.
-
HTML-AAM: decide the fate of the UIA-Express column w3c/aria#268, by @cyns.
-
ARIA 1.1 link to UAAG points to UAAG 1. w3c/aria#265, by @fredesch.
-
Inconsistent use of tool bar vs. toolbar w3c/aria#263, by @ZoeBijl.
-
Simplify usage of kbd element w3c/aria#261, by @ZoeBijl.
-
HTML-AAM - test and update name calc for labelable elements w3c/aria#259, by @stevefaulkner.
-
HTML-AAM link to github issue tracker w3c/aria#258, by @stevefaulkner.
-
Add links to code examples w3c/aria#255, by @ZoeBijl.
-
Fix broken links to examples w3c/aria#254, by @ZoeBijl.
-
HTML-AAM: missing section ids in Name and Description Calculation w3c/aria#253, by @cyns.
-
HTML-AAM: Make presentation of UIA mapping properties consistent w3c/aria#252, by @jasonkiss.
-
retire - put health warning on WAI-ARIA Primer 1.0 w3c/aria#249, by @stevefaulkner.
-
Needs mappings for datetime-local w3c/aria#248, by @dstorey.
-
CORE-AAM: UIA mapping for role=region w3c/aria#243, by @cyns.
-
CORE-AAM: UIA mapping for role=navigation w3c/aria#242, by @cyns.
-
APG - Non-Modal Dialog needs to specify how move should work w3c/aria#241, by @jnurthen.
-
HTML-AAM: how to map Inner Phrasing Content for <meter>? w3c/aria#240, by @cyns.
-
54 issues closed in the SVG Accessibility Task Force.
-
HTML-AAM: UIA mappings for <footer> w3c/aria#152.
-
html-aam: UIA mapping for <mark> w3c/aria#175.
-
HTML-AAM: input type=time UIA mapping incorrect w3c/aria#168.
-
HTML-AAM: UIA mapping for <meter> w3c/aria#176.
-
HTML-AAM: change @accesskey UIA mapping w3c/aria#182.
-
HMTL-AAM: UIA mapping for @hidden w3c/aria#185.
-
HTML-AAM: UIA mapping for @high on <meter> w3c/aria#186.
-
HTML-AAM: UIA mapping for @href on a, area w3c/aria#187.
-
HTML-AAM: determine best UIA mapping for @href on <link> w3c/aria#188.
-
HTML-AAM: UIA mapping for @label w3c/aria#190.
-
HTML-AAM: UIA mapping for @reveresed on ol w3c/aria#196.
-
HTML-AAM: UIA mapping for @step w3c/aria#197.
-
HTML-AAM: UIA mapping for @value on input w3c/aria#200.
-
HTML-AAM: UIA mapping for @value on li w3c/aria#201.
-
ARIA 1.1 link to UAAG points to UAAG 1. w3c/aria#265.
-
HTML-AAM: UIA mapping for <table> w3c/aria#179.
-
Should taskforce be two words? w3c/aria#221.
-
Simplify usage of kbd element w3c/aria#261.
-
Add links to code examples w3c/aria#255.
-
Inconsistent use of tool bar vs. toolbar w3c/aria#263.
-
WAR-ARIA 1.1: Update old HTML5 links w3c/aria#122.
-
WAI-ARIA 1.1: Link to DOM2 Core w3c/aria#118.
-
Fix broken links to examples w3c/aria#254.
-
HTML-AAM link to github issue tracker w3c/aria#258.
-
HTML-AAM: input type=password UIA mapping w3c/aria#165.
-
HTML-AAM: UIA mappings for <input type=file> w3c/aria#162.
-
HTML-AAM: change <iframe> UIA mapping to Pane w3c/aria#156.
-
HTML-AAM: <header> UIA mapping w3c/aria#154.
-
Correct spelling of tabbable? w3c/aria#225.
-
Focusability of disabled menu items w3c/aria#215.
-
Usage of <hr> between <section>'s w3c/aria#228.
-
HTML-AAM: UIA mapping for <section> w3c/aria#178.
-
HTML-AAM: UIA mappings for input type=url w3c/aria#169.
-
HTML-AAM: input type=search UIA mapping w3c/aria#167.
-
HTML-AAM: input type=number UIA mapping w3c/aria#164.
-
Html-aam ATK mapping for METER element w3c/aria#150.
-
Remove or edit “HTML 5 - A look ahead” w3c/aria#216.
-
HTML-AAM: <div> UIA mapping is Control Type: Group w3c/aria#147.
-
HTML-AAM: audio UIA should have localized control type w3c/aria#138.
-
HTML-AAM: <dialog> should map to aria role=dialog w3c/aria#146.
-
HTML-AAM: <br> change "?" to "Not Mapped" w3c/aria#140.
-
HTML-AAM: UIA mapping for input type=telephone w3c/aria#236.
-
HTML-AAM: update UIA mapping for aside w3c/aria#230.
-
HTML-AAM: UIA mapping for <figure> w3c/aria#232.
-
HTML-AAM: UIA mapping for <main> w3c/aria#237.
-
HTML-AAM: change <datalist> UIA mapping w3c/aria#231.
-
CORE-AAM: UIA mapping for role=main w3c/aria#238.
-
-
3 issues reopened in the SVG Accessibility Task Force.
-
HTML-AAM: UIA mappings for <footer> w3c/aria#152, by @cyns.
-
HTML-AAM: add polite live region to UIA mapping for <output> w3c/aria#234, by @stevefaulkner.
-
-
64 issues in the SVG Accessibility Task Force received 117 new comments.
-
Should tab panels activate on focus? w3c/aria#206 (6 comments by @becka11y, @mcking65, @StommePoes, @ZoeBijl)
-
retire - put health warning on WAI-ARIA Primer 1.0 w3c/aria#249 (6 comments by @edouard-lopez, @jasonkiss, @mcking65, @richschwer, @ZoeBijl)
-
HTML-AAM: <datalist> used with non-textbox inputs shouldn't map to aria listbox role w3c/aria#233 (4 comments by @cyns, @klown)
-
HTML-AAM: remove Calendar mapping from input in date, date/time, month, week w3c/aria#158 (2 comments by @cyns, @jasonkiss)
-
HTML-AAM: suggestion: add "see also NAME-AAM" to image alt is empty w3c/aria#157 (2 comments by @cyns, @jasonkiss)
-
HTML-AAM: missing section ids in Name and Description Calculation w3c/aria#253 (2 comments by @cyns, @jasonkiss)
-
SVG-AAM: Issues with the use of title attribute in name and description calculation w3c/aria#137 (2 comments by @fredesch)
-
HTML-AAM: <footer> that is not child of body should not be group in UIA w3c/aria#151 (2 comments by @jasonkiss, @stevefaulkner)
-
HTML-AAM: audio UIA should have localized control type w3c/aria#138 (2 comments by @cyns, @jasonkiss)
-
HTML-AAM: add polite live region to UIA mapping for <output> w3c/aria#234 (2 comments by @cyns, @stevefaulkner)
-
RFE: Add means to programmatically control link creation for rref, pref, sref, and glossary references w3c/aria#106 (1 comment by @joanmarie)
-
HTML-AAM - test and update name calc for labelable elements w3c/aria#259 (1 comment by @stevefaulkner)
-
w3c/aria#61 (1 comment by @ZoeBijl)
-
HTML-AAM: determine right UIA mapping for browser generated form validation error messages w3c/aria#160 (1 comment by @jasonkiss)
-
html-AAM: remove aria-role and string stuff from <footer> UIA mapping w3c/aria#153 (1 comment by @jasonkiss)
-
HTML-AAM: <input type=email> add localized control type = "email" for UIA w3c/aria#161 (1 comment by @cyns)
-
HTML-AAM: <dfn> UIA mapping to group with localized control type and text style w3c/aria#145 (1 comment by @jasonkiss)
-
14 pull requests opened in the SVG Accessibility Task Force.
-
updates to UIA mappings for ARIA landmark roles w3c/aria#272, by @cyns.
-
Bunch of UIA mappings w3c/aria#267, by @cyns.
-
Migrated to latest terms cleanup code w3c/aria#264, by @halindrome.
-
Update DOM reference w3c/aria#262, by @ZoeBijl.
-
Make 'file bug' link point to GitHub w3c/aria#260, by @ZoeBijl.
-
updated template/added url for link role w3c/aria#257, by @a11ydoer.
-
ReSpec event handler to fix scrolling when loading. w3c/aria#256, by @klown.
-
issues: 161, 164, 167, 169, 178 w3c/aria#251, by @cyns.
-
Remove section A2.5 HTML 5 A look ahead w3c/aria#250, by @ZoeBijl.
-
UIA mappings for header (issue 154) w3c/aria#247, by @cyns.
-
UIA mapping for figure (issue 232) w3c/aria#245, by @cyns.
-
adding uia mappings for aside (issue 230) w3c/aria#244, by @cyns.
-
Editorial: Fix typos w3c/aria#239, by @prayagverma.
-
-
9 pull requests merged in the SVG Accessibility Task Force.
-
Bunch of UIA mappings w3c/aria#267.
-
Changed reference conversion logic w3c/aria#108.
-
Update DOM reference w3c/aria#262.
-
Make 'file bug' link point to GitHub w3c/aria#260.
-
Editorial: Fix typos w3c/aria#239.
-
Remove section A2.5 HTML 5 A look ahead w3c/aria#250.
-
issues: 161, 164, 167, 169, 178 w3c/aria#251.
-
UIA mappings for header (issue 154) w3c/aria#247.
-
UIA mapping for figure (issue 232) w3c/aria#245.
-
-
5 pull requests closed in the SVG Accessibility Task Force.
-
adding uia mappings for aside (issue 230) w3c/aria#244.
-
Issue 152 w3c/aria#246.
-
Changed logic to preserve referenced items. w3c/aria#112.
-
Update DOM reference w3c/aria#121.
-
updated template/added url for link role w3c/aria#257.
-
-
10 pull requests in the SVG Accessibility Task Force received 25 new comments.
-
ReSpec event handler to fix scrolling when loading. w3c/aria#256 (10 comments by @halindrome, @klown, @ZoeBijl)
-
Participants
-
1 participant joined.
-
Mark Sadecki (W3C Invited Experts) joined.
-
GitHub
w3c/svgwg
-
11 issues opened.
-
`d` geometric property needs a clear & extensible name w3c/svgwg#49, by @AmeliaBR.
-
Linking: ID + SVGViewSpec? w3c/svgwg#48, by @nikosandronikos.
-
should UA style sheet have a rule for visited link color? w3c/svgwg#47, by @heycam.
-
Remove `version` attribute from code samples w3c/svgwg#45, by @AmeliaBR.
-
Does conditional processing mute sound playback? w3c/svgwg#44, by @karip.
-
5 issues closed.
-
Remove `version` attribute from code samples w3c/svgwg#45.
-
Remove SVGZoomEvent? w3c/svgwg#21.
-
18 issues received 40 new comments.
-
Clarify how user agents should implement vendor-specific extensions w3c/svgwg#53 (6 comments by @AmeliaBR, @jarek-foksa, @nikosandronikos, @tabatkins)
-
How should degenerate closed paths render in SVG ? w3c/svgwg#42 (4 comments by @karip, @nikosandronikos)
-
should UA style sheet have a rule for visited link color? w3c/svgwg#47 (4 comments by @dkturner, @heycam, @progers)
-
Add layers with Z-index and blending filters for layers composition and animation. w3c/svgwg#43 (3 comments by @Emasoft, @nikosandronikos)
-
Should SVG keep or drop dominant-baseline values not supported by CSS? w3c/svgwg#31 (3 comments by @AmeliaBR, @nikosandronikos)
-
Directly referencing the HTML Sequential focus navigation and tabindex w3c/svgwg#50 (2 comments by @richschwer, @tabatkins)
-
Should SVGMarkerElement.setOrientTo{Auto|Angle} really affect the attribute? w3c/svgwg#46 (2 comments by @heycam, @nikosandronikos)
-
Error Processing should talk about when to use initial values for attributes w3c/svgwg#52 (1 comment by @sideshowbarker)
-
Should SVG define the exact rendered result for a stroke? w3c/svgwg#41 (1 comment by @nikosandronikos)
-
GitHub
w3c/svgwg
-
14 issues opened.
-
How should degenerate closed paths render in SVG ? w3c/svgwg#42, by @nikosandronikos.
-
Should SVG define the exact rendered result for a stroke? w3c/svgwg#41, by @nikosandronikos.
-
Full glyph cell term is not defined w3c/svgwg#40, by @nikosandronikos.
-
How is the first glyph positioned in a line? w3c/svgwg#39, by @nikosandronikos.
-
How to fill text sequentially into multiple shapes? w3c/svgwg#38, by @nikosandronikos.
-
How does wrap-flow apply when a shape has holes? w3c/svgwg#37, by @nikosandronikos.
-
How to handle overflow for text in a shape? w3c/svgwg#36, by @nikosandronikos.
-
Where to position the first line of text in a shape? w3c/svgwg#35, by @nikosandronikos.
-
Adding default values for hanging and mathematical baselines w3c/svgwg#34, by @nikosandronikos.
-
Clarify behaviour of baseline tables when changing font size w3c/svgwg#32, by @nikosandronikos.
-
How does SVG text interact with CSS? w3c/svgwg#30, by @nikosandronikos.
-
5 issues closed.
-
SYMM Working Groups w3c/svgwg#6.
-
Conformance, declarative animation w3c/svgwg#23.
-
Documentation should mention SMIL polyfill w3c/svgwg#24.
-
Add support for data-* attributes on all svg elements w3c/svgwg#27.
-
-
7 issues received 13 new comments.
-
How should degenerate closed paths render in SVG ? w3c/svgwg#42 (4 comments by @heycam, @nikosandronikos)
-
Add support for data-* attributes on all svg elements w3c/svgwg#27 (2 comments by @cvrebert, @heycam)
-
Add layers with Z-index and blending filters for layers composition and animation. w3c/svgwg#43 (1 comment by @nikosandronikos)
-
Should SVG define the exact rendered result for a stroke? w3c/svgwg#41 (1 comment by @nikosandronikos)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
108 issues opened in the SVG Accessibility Task Force.
-
CORE-AAM: UIA mapping for role=main w3c/aria#238, by @cyns.
-
HTML-AAM: UIA mapping for <main> w3c/aria#237, by @cyns.
-
HTML-AAM: UIA mapping for input type=telephone w3c/aria#236, by @cyns.
-
HTML-AAM: UIA mapping for <time> element w3c/aria#235, by @cyns.
-
HTML-AAM: add polite live region to UIA mapping for <output> w3c/aria#234, by @cyns.
-
HTML-AAM: UIA mapping for <figure> w3c/aria#232, by @cyns.
-
HTML-AAM: change <datalist> UIA mapping w3c/aria#231, by @cyns.
-
HTML-AAM: update UIA mapping for aside w3c/aria#230, by @cyns.
-
Usage of <hr> between <section>'s w3c/aria#228, by @ZoeBijl.
-
Replace <hr /> with <hr> w3c/aria#227, by @ZoeBijl.
-
Definition of Internationalizable w3c/aria#226, by @ZoeBijl.
-
Correct spelling of tabbable? w3c/aria#225, by @ZoeBijl.
-
Various typos w3c/aria#224, by @ZoeBijl.
-
textbox should be two words w3c/aria#223, by @ZoeBijl.
-
multiselectable should be two words w3c/aria#222, by @ZoeBijl.
-
Should taskforce be two words? w3c/aria#221, by @ZoeBijl.
-
Typos in introduction w3c/aria#220, by @ZoeBijl.
-
Typo in editors note w3c/aria#219, by @ZoeBijl.
-
Missing space in Status of This Document w3c/aria#218, by @ZoeBijl.
-
Remove todo from 4.1.5 Example Keyboard Operation: Radio Group/Radio w3c/aria#217, by @ZoeBijl.
-
Remove or edit “HTML 5 - A look ahead” w3c/aria#216, by @ZoeBijl.
-
Focusability of disabled menu items w3c/aria#215, by @ZoeBijl.
-
Which pieces need to be filled in to trigger script w3c/aria#214, by @ZoeBijl.
-
When casing is relevant, casing preferences w3c/aria#211, by @ZoeBijl.
-
How the ¨tying together script¨ works w3c/aria#210, by @ZoeBijl.
-
How to use the taxonomy to extend roles effectively w3c/aria#208, by @ZoeBijl.
-
Role name patterns w3c/aria#207, by @ZoeBijl.
-
Should tab panels activate on focus? w3c/aria#206, by @becka11y.
-
Remove xml declaration from APG document w3c/aria#205, by @ZoeBijl.
-
Create tab panel code example w3c/aria#204, by @ZoeBijl.
-
Enforce beautify standards and validate code to catch mistakes w3c/aria#202, by @ZoeBijl.
-
HTML-AAM: UIA mapping for @value on li w3c/aria#201, by @cyns.
-
HTML-AAM: UIA mapping for @value on input w3c/aria#200, by @cyns.
-
HTML-AAM: UIA mapping for @step w3c/aria#197, by @cyns.
-
HTML-AAM: UIA mapping for @reveresed on ol w3c/aria#196, by @cyns.
-
HTML-AAM: should @longdesc be part of name calculation? w3c/aria#195, by @cyns.
-
HTML-AAM: determine best UIA mapping for @longdesc w3c/aria#194, by @cyns.
-
HTML-AAM: should @list map to aria-controls? w3c/aria#193, by @cyns.
-
HTML-AAM: UIA mapping for @list w3c/aria#192, by @cyns.
-
HTML-AAM: UIA mapping for @lang w3c/aria#191, by @cyns.
-
HTML-AAM: UIA mapping for @label w3c/aria#190, by @cyns.
-
HTML-AAM: suggestion: add "see also NAME-AAM" to @label w3c/aria#189, by @cyns.
-
HTML-AAM: determine best UIA mapping for @href on <link> w3c/aria#188, by @cyns.
-
HTML-AAM: UIA mapping for @href on a, area w3c/aria#187, by @cyns.
-
HTML-AAM: UIA mapping for @high on <meter> w3c/aria#186, by @cyns.
-
HMTL-AAM: UIA mapping for @hidden w3c/aria#185, by @cyns.
-
HTML-AAM: should @headers participate in name calculation? w3c/aria#184, by @cyns.
-
HTML-AAM: determine how to map @accesskey <1 character to UIA w3c/aria#183, by @cyns.
-
HTML-AAM: change @accesskey UIA mapping w3c/aria#182, by @cyns.
-
HTML-AAM: @abbr should be part of name calculation w3c/aria#181, by @cyns.
-
HTML-AAM: UIA mapping for <tr> w3c/aria#180, by @cyns.
-
HTML-AAM: UIA mapping for <table> w3c/aria#179, by @cyns.
-
HTML-AAM: UIA mapping for <section> w3c/aria#178, by @cyns.
-
HTML-AAM: add note about UIA mapping to "Text" w3c/aria#177, by @cyns.
-
HTML-AAM: UIA mapping for <meter> w3c/aria#176, by @cyns.
-
html-aam: UIA mapping for <mark> w3c/aria#175, by @cyns.
-
Code Examples: Validate HTML and CSS w3c/aria#174, by @ZoeBijl.
-
HTML-AAM: should <legend> map to aria role=label? w3c/aria#173, by @cyns.
-
HTML-AAM: UIA mapping for <legend> w3c/aria#172, by @cyns.
-
HTML-AAM: UIA mapping for <label> w3c/aria#171, by @cyns.
-
HTML-AAM: determine best UIA mapping for <kbd> w3c/aria#170, by @cyns.
-
HTML-AAM: UIA mappings for input type=url w3c/aria#169, by @cyns.
-
HTML-AAM: input type=time UIA mapping incorrect w3c/aria#168, by @cyns.
-
HTML-AAM: input type=search UIA mapping w3c/aria#167, by @cyns.
-
ARIA: should there be a password role? w3c/aria#166, by @cyns.
-
HTML-AAM: input type=password UIA mapping w3c/aria#165, by @cyns.
-
HTML-AAM: input type=number UIA mapping w3c/aria#164, by @cyns.
-
HTML-AAM: UIA mappings for <input type=file> w3c/aria#162, by @cyns.
-
HTML-AAM: add UIA LabeledBy info to input types w3c/aria#159, by @cyns.
-
HTML-AAM: suggestion: add "see also NAME-AAM" to image alt is empty w3c/aria#157, by @cyns.
-
HTML-AAM: change <iframe> UIA mapping to Pane w3c/aria#156, by @cyns.
-
HTML-AAM: <header> UIA mapping w3c/aria#154, by @cyns.
-
html-AAM: remove aria-role and string stuff from <footer> UIA mapping w3c/aria#153, by @cyns.
-
HTML-AAM: UIA mappings for <footer> w3c/aria#152, by @cyns.
-
HTML-AAM: <footer> that is not child of body should not be group in UIA w3c/aria#151, by @cyns.
-
Html-aam ATK mapping for METER element w3c/aria#150, by @klown.
-
HTML-AAM: should <figcaption> be mapped to aria role=label? w3c/aria#149, by @cyns.
-
HTML-AAM: mappings for dd, dt, dl seem insuficient w3c/aria#148, by @cyns.
-
HTML-AAM: <div> UIA mapping is Control Type: Group w3c/aria#147, by @cyns.
-
HTML-AAM: <dialog> should map to aria role=dialog w3c/aria#146, by @cyns.
-
HTML-AAM: should <dfn> map to aria role=definition? w3c/aria#144, by @cyns.
-
HTML-AAM: should <details> map to aria role=dialog? w3c/aria#143, by @cyns.
-
HTML-AAM: should <caption> map to aria role=label? w3c/aria#142, by @cyns.
-
HTML-AAM: should we have some general language for sub-doms? w3c/aria#141, by @cyns.
-
HTML-AAM: <br> change "?" to "Not Mapped" w3c/aria#140, by @cyns.
-
HTML-AAM: blockquote UIA should have localized control type w3c/aria#139, by @cyns.
-
HTML-AAM: audio UIA should have localized control type w3c/aria#138, by @cyns.
-
SVG-AAM: Mesh is missing from the mapping table w3c/aria#135, by @fredesch.
-
SVG-AAM: Corrections to platform mappings for ATK w3c/aria#133, by @joanmarie.
-
APG: Tidy up APG HTML w3c/aria#131, by @ZoeBijl.
-
APG: Add bread crumb design pattern w3c/aria#130, by @ZoeBijl.
-
WAI-ARIA 1.1: base concepts link to HTML 4 w3c/aria#129, by @ZoeBijl.
-
-
15 issues closed in the SVG Accessibility Task Force.
-
Replace <hr /> with <hr> w3c/aria#227.
-
Missing space in Status of This Document w3c/aria#218.
-
textbox should be two words w3c/aria#223.
-
multiselectable should be two words w3c/aria#222.
-
Typos in introduction w3c/aria#220.
-
Typo in editors note w3c/aria#219.
-
Various typos w3c/aria#224.
-
Remove xml declaration from APG document w3c/aria#205.
-
APG: Tidy up APG HTML w3c/aria#131.
-
Code Examples: Validate HTML and CSS w3c/aria#174.
-
Using the form’s role attribute w3c/aria#85.
-
SVG-AAM: Mesh is missing from the mapping table w3c/aria#135.
-
ARIA 1.1 should incorporate some DPUB roles w3c/aria#51.
-
WAI-ARIA: add role value image as synonym for img w3c/aria#116.
-
27 issues in the SVG Accessibility Task Force received 115 new comments.
-
ARIA: should there be a password role? w3c/aria#166 (21 comments by @cookiecrook, @cyns, @jnurthen, @joanmarie, @jonathanKingston, @stevefaulkner, @ZoeBijl)
-
Should tab panels activate on focus? w3c/aria#206 (12 comments by @becka11y, @jnurthen, @klown, @ZoeBijl)
-
SVG-AAM: Corrections to platform mappings for ATK w3c/aria#133 (11 comments by @AmeliaBR, @fredesch, @joanmarie, @klown, @richschwer)
-
SVG-AAM / Core AAM: Consider explicit language regarding objects with presentational role and ARIA attributes w3c/aria#136 (11 comments by @fredesch, @joanmarie, @klown, @richschwer)
-
SVG-AAM: Issues with the use of title attribute in name and description calculation w3c/aria#137 (7 comments by @fredesch, @joanmarie)
-
Enforce beautify standards and validate code to catch mistakes w3c/aria#202 (6 comments by @jnurthen, @ZoeBijl)
-
SVG-AAM: Consider explicit language regarding inclusion of elements with child title or desc w3c/aria#134 (5 comments by @fredesch, @joanmarie, @richschwer)
-
HTML-AAM: @title on <abbr> and <dfn> needs to be covered in name calculation w3c/aria#199 (3 comments by @cyns, @ZoeBijl)
-
Remove todo from 4.1.5 Example Keyboard Operation: Radio Group/Radio w3c/aria#217 (1 comment by @ZoeBijl)
-
-
2 pull requests opened in the SVG Accessibility Task Force.
-
Add Michiel Bijl as editor w3c/aria#203, by @ZoeBijl.
-
Add a Gitter chat badge to README.md w3c/aria#132, by @gitter-badger.
-
-
2 pull requests merged in the SVG Accessibility Task Force.
-
Add Michiel Bijl as editor w3c/aria#203.
-
Feature/radio generated w3c/aria#126.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
Add a Gitter chat badge to README.md w3c/aria#132.
-