SVG Working Group - Activity in 2017
No matches.
GitHub
w3c/svgwg
-
4 issues opened.
-
Make textLength property on <text> and <tspan> a styleable property w3c/svgwg#375, by @BigBadaboom.
-
Add decode() and decoding attribute to SVGImageElement w3c/svgwg#373, by @vmpstr.
-
Implicit and allowed roles for SVG element in a HTML document w3c/svgwg#372, by @lemnis.
-
:hover on overlapping elements w3c/svgwg#371, by @NtuFlorimond.
-
-
1 issue reopened.
-
7 issues received 21 new comments.
-
SVG2 spec means elements within a <use> tag can not be targeted for styling w3c/svgwg#367 (7 comments by @AmeliaBR, @bureau-of-information, @dholbert, @peter-mouland)
-
Update WebIDL definition(s) to use new mixin syntax w3c/svgwg#353 (6 comments by @dirkschulze, @tobie)
-
Add decode() and decoding attribute to SVGImageElement w3c/svgwg#373 (2 comments by @AmeliaBR, @smfr)
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (2 comments by @fuchsia, @tabatkins)
-
'd' presentation attribute inconsistent with shipped implementation and offset-path w3c/svgwg#320 (1 comment by @alexjlockwood)
-
-
2 pull requests opened.
-
'd' presentation attribute: use path() function w3c/svgwg#374, by @ewilligers.
-
1 pull request merged.
-
Fix typo: "it its" -> "its" w3c/svgwg#368.
-
-
2 pull requests received 10 new comments.
-
Update SVG interfaces to use mixins where possible in all SVG specs. Issue #353 w3c/svgwg#376 (9 comments by @dirkschulze, @plinss, @tobie)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
7 issues opened in the SVG Accessibility Task Force.
-
ARIA 1.1 inconsistent progressbar superclass w3c/aria#686, by @xi.
-
Aria 1.1 external file : XSD, RDF/XML should be put on github w3c/aria#685, by @innovimax.
-
name from author/content woes w3c/aria#683, by @stevefaulkner.
-
Need to check roles which support aria-expanded w3c/aria#681, by @joanmarie.
-
Need clarity on computation involving first traversal w3c/aria#676, by @devarshipant.
-
RDF model still useful? w3c/aria#672, by @michael-n-cooper.
-
-
5 issues closed in the SVG Accessibility Task Force.
-
Graphics AAM: Verify UIA mappings w3c/aria#663.
-
Need clarity on computation involving first traversal w3c/aria#676.
-
7 issues in the SVG Accessibility Task Force received 12 new comments.
-
Aria 1.1 external file : XSD, RDF/XML should be put on github w3c/aria#685 (2 comments by @innovimax, @michael-n-cooper)
-
Need clarity on computation involving first traversal w3c/aria#676 (2 comments by @devarshipant, @joanmarie)
-
4.3 Text Alternative Computation (using placeholder attribute) w3c/aria#643 (1 comment by @joanmarie)
-
8 pull requests opened in the SVG Accessibility Task Force.
-
remove extra </a> w3c/aria#682, by @innovimax.
-
<!-- not allowed inside comment w3c/aria#678, by @innovimax.
-
use specref version of EPUB-SSV, MSAA, UIA-Express, UI-Automation w3c/aria#677, by @innovimax.
-
update to xmlschema 1.1 instead of 1.0 w3c/aria#675, by @innovimax.
-
update SVG2 to CR w3c/aria#674, by @innovimax.
-
add missing space w3c/aria#673, by @innovimax.
-
-
7 pull requests merged in the SVG Accessibility Task Force.
-
remove extra </a> w3c/aria#682.
-
update to xmlschema 1.1 instead of 1.0 w3c/aria#675.
-
add missing space w3c/aria#673.
-
Graphics AAM: Fix macOS mapping for graphics-symbol w3c/aria#666.
-
5 pull requests closed in the SVG Accessibility Task Force.
-
Update Practices references w3c/aria#616.
-
<!-- not allowed inside comment w3c/aria#678.
-
update SVG2 to CR w3c/aria#674.
-
Update UIA mappings for Graphics AAM w3c/aria#664.
-
-
1 pull request reopened in the SVG Accessibility Task Force.
-
<!-- not allowed inside comment w3c/aria#678, by @innovimax.
-
-
9 pull requests in the SVG Accessibility Task Force received 14 new comments.
-
use specref version of EPUB-SSV, MSAA, UIA-Express, UI-Automation w3c/aria#677 (2 comments by @innovimax, @joanmarie)
-
ARIA 1.2: Add explicit guidance for non-pertinent errormessage elemen… w3c/aria#680 (1 comment by @joanmarie)
SVG Accessibility Task Force
GitHub
w3c/aria
-
12 issues opened in the SVG Accessibility Task Force.
-
article role does not support aria-level w3c/aria#669, by @jongund.
-
REFID and Shadow DOM w3c/aria#668, by @sspi.
-
Graphics AAM: Verify UIA mappings w3c/aria#663, by @joanmarie.
-
Adding roles, states, and properties to support math w3c/aria#660, by @dani31415.
-
accname-aam clarify hidden w3c/aria#658, by @jnurthen.
-
[PR-dpub-aria-1.0-20171102] example 34 typo w3c/aria#657, by @notabene.
-
[PR-dpub-aria-1.0-20171102] “illustratration” typo w3c/aria#656, by @notabene.
-
2 issues closed in the SVG Accessibility Task Force.
-
REFID and Shadow DOM w3c/aria#668.
-
-
9 issues in the SVG Accessibility Task Force received 16 new comments.
-
Adding roles, states, and properties to support math w3c/aria#660 (5 comments by @asurkov, @dani31415, @joanmarie, @pkra)
-
Need aria-rowtext, aria-coltext for name of row/col in spreadsheet w3c/aria#667 (2 comments by @asurkov, @minorninth)
-
Datepicker requirements no longer available due to 1.0 page redirection w3c/aria#655 (2 comments by @heidi-jungel, @joanmarie)
-
-
5 pull requests opened in the SVG Accessibility Task Force.
-
Graphics AAM: Fix macOS mapping for graphics-symbol w3c/aria#666, by @joanmarie.
-
Update UIA mappings for Graphics AAM w3c/aria#664, by @boggydigital.
-
Graphics AAM: Fix IAccessible2 mapping typo w3c/aria#662, by @joanmarie.
-
Graphics AAM: Fix ATK mappings w3c/aria#661, by @joanmarie.
-
-
3 pull requests merged in the SVG Accessibility Task Force.
-
Graphics AAM: Fix IAccessible2 mapping typo w3c/aria#662.
-
Graphics AAM: Fix ATK mappings w3c/aria#661.
-
3 pull requests in the SVG Accessibility Task Force received 4 new comments.
GitHub
w3c/svgwg
-
18 issues opened.
-
Origin of CSS transform for svg:use w3c/svgwg#370, by @NtuFlorimond.
-
Values of width/height = auto w3c/svgwg#369, by @AmeliaBR.
-
'color-interpolation' isn't used for alpha compositing w3c/svgwg#366, by @litherum.
-
Move Web Animations out of normative references w3c/svgwg#365, by @ewilligers.
-
Remove Paths additions that were copied to SVG Paths specification w3c/svgwg#364, by @boggydigital.
-
Change the use element shadow tree to closed w3c/svgwg#363, by @boggydigital.
-
Convert SVG linking reftests to .svg files w3c/svgwg#362, by @boggydigital.
-
'image' element not defined to fire 'load' event when load happens w3c/svgwg#361, by @gsnedders.
-
Clean up definitions around transforms on root SVG element w3c/svgwg#360, by @boggydigital.
-
Color chapter was trimmed down to CSS Color 3 and 4 refs w3c/svgwg#359, by @svgeesus.
-
SVG Integration: expose mode on document somehow w3c/svgwg#358, by @annevk.
-
SVG Integration: mixed content w3c/svgwg#357, by @annevk.
-
SVG Integration: update "This version" link w3c/svgwg#356, by @annevk.
-
Please link to GitHub from the drafts w3c/svgwg#355, by @annevk.
-
Initial value of pattern elements width/height is incorrect w3c/svgwg#354, by @dirkschulze.
-
Update WebIDL definition(s) to use new mixin syntax w3c/svgwg#353, by @tobie.
-
White-space only text nodes. w3c/svgwg#352, by @Tavmjong.
-
-
3 issues closed.
-
Origin of CSS transform for svg:use w3c/svgwg#370.
-
Values of width/height = auto w3c/svgwg#369.
-
Initial value of pattern elements width/height is incorrect w3c/svgwg#354.
-
-
11 issues received 28 new comments.
-
Initial value of pattern elements width/height is incorrect w3c/svgwg#354 (4 comments by @BigBadaboom, @dirkschulze, @fsoder)
-
Add getScreenBBox() method to SVGGraphicsElement interface w3c/svgwg#76 (3 comments by @BigBadaboom, @fsoder, @paradisaeidae)
-
'color-interpolation' isn't used for alpha compositing w3c/svgwg#366 (3 comments by @litherum, @svgeesus)
-
SVG2 spec means elements within a <use> tag can not be targeted for styling w3c/svgwg#367 (2 comments by @AmeliaBR, @peter-mouland)
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (2 comments by @fuchsia, @tabatkins)
-
Remove Paths additions that were copied to SVG Paths specification w3c/svgwg#364 (2 comments by @AmeliaBR, @ewilligers)
-
1 pull request opened.
-
Fix typo: "it its" -> "its" w3c/svgwg#368, by @jmdyck.
-
-
1 pull request received 2 new comments.
GitHub
w3c/svgwg
-
4 issues opened.
-
Reserialization of SVGStringList for comma-separated values w3c/svgwg#351, by @Zirro.
-
Super svg path defined by children path w3c/svgwg#350, by @NtuFlorimond.
-
Resolved value for the 'width' and 'height' geometry properties w3c/svgwg#349, by @fsoder.
-
Allow setting the SVG context properties when in an HTML <img> tag w3c/svgwg#348, by @ExE-Boss.
-
-
5 issues received 21 new comments.
-
Resolved value for the 'width' and 'height' geometry properties w3c/svgwg#349 (6 comments by @AmeliaBR, @fsoder)
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (5 comments by @fuchsia, @tabatkins, @zed-vector)
-
Allow setting the SVG context properties when in an HTML <img> tag w3c/svgwg#348 (2 comments by @heycam, @tabatkins)
SVG Accessibility Task Force
GitHub
w3c/aria
-
4 issues opened in the SVG Accessibility Task Force.
-
[DPUB] subtitle name from contents w3c/aria#654, by @mattgarrish.
-
[DPUB] typo in name from field w3c/aria#653, by @mattgarrish.
-
[DPUB] incorrect superclass for doc-pullquote w3c/aria#652, by @mattgarrish.
-
ARIA: how to handle large numbers w3c/aria#650, by @adamliptrot-oc.
-
-
6 issues closed in the SVG Accessibility Task Force.
-
[DPUB] typo in name from field w3c/aria#653.
-
WAI-ARIA 1.1 and DPUB-ARIA 1.0 in BlueGriffon w3c/aria#505.
-
DPUB-ARIA abstract is too broad w3c/aria#502.
-
ARIA: how to handle large numbers w3c/aria#650.
-
-
6 issues in the SVG Accessibility Task Force received 7 new comments.
-
ARIA: Editorial cleanup needed to "Presentational Roles Conflict Resolution" section w3c/aria#646 (1 comment by @joanmarie)
-
Confusing notation in definition of attributes introduced in ARIA 1.1 w3c/aria#406 (1 comment by @joanmarie)
-
ARIA 1.2: Explicit guidance needed for non-pertinent errormessage elements w3c/aria#587 (1 comment by @joanmarie)
-
Allow null value of aria-activedescendent when element does not have DOM focus w3c/aria#501 (1 comment by @mcking65)
Participants
-
1 organization joined.
-
HM Government joined.
-
GitHub
w3c/svgwg
-
3 issues opened.
-
The SVG2 points-attribute is not backwardly-compatible with SVG1.1 w3c/svgwg#347, by @fuchsia.
-
Add [Exposed] to all interfaces w3c/svgwg#345, by @annevk.
-
fill-rule Could Use Some Clarification w3c/svgwg#344, by @patrickdark.
-
-
1 issue closed.
-
8 issues received 18 new comments.
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335 (6 comments by @AmeliaBR, @fuchsia, @svgeesus)
-
fill-rule Could Use Some Clarification w3c/svgwg#344 (4 comments by @AmeliaBR, @patrickdark, @svgeesus)
-
Serialization format for path strings w3c/svgwg#321 (3 comments by @AmeliaBR, @ewilligers, @tabatkins)
-
The SVG2 points-attribute is not backwardly-compatible with SVG1.1 w3c/svgwg#347 (1 comment by @AmeliaBR)
-
Allow stroke-dasharray/dashoffset % to be specified relative to path length w3c/svgwg#177 (1 comment by @AmeliaBR)
-
-
1 pull request opened.
-
Fixed path grammar w3c/svgwg#346, by @fuchsia.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
5 issues opened in the SVG Accessibility Task Force.
-
Using pos-inset and aria-setsize with a toolbar w3c/aria#649, by @taylorcyoung.
-
aria-* and filtering a grid w3c/aria#648, by @knoobie.
-
Core-AAM: Remove ARIA 1.1 notes from macOS mapping column w3c/aria#645, by @cookiecrook.
-
-
9 issues closed in the SVG Accessibility Task Force.
-
aria-* and filtering a grid w3c/aria#648.
-
CORE-AAM: term role mappings restrict use to list item w3c/aria#455.
-
-
16 issues in the SVG Accessibility Task Force received 27 new comments.
-
CORE-AAM: Add conditional platform mappings for nameless forms w3c/aria#514 (3 comments by @joanmarie, @matatk)
-
ARIA: Editorial cleanup needed to "Presentational Roles Conflict Resolution" section w3c/aria#646 (2 comments by @joanmarie, @mcking65)
-
Core-AAM: Need to verify, expand upon, and/or correct AX API aria-activedescendant exposure w3c/aria#598 (2 comments by @cookiecrook, @joanmarie)
-
[core-aam] Rule for excluding elements with children presentational true is out of date w3c/aria#493 (1 comment by @joanmarie)
-
Core AAM: Clarify expectations regarding implementation of IAccessible::accSelect() w3c/aria#612 (1 comment by @joanmarie)
-
Core-AAM: AXPress and AXShowMenu on aria-haspopup is potentially misleading/confusing w3c/aria#570 (1 comment by @joanmarie)
-
CORE-AAM: cell mapping specifies TableItem as UIA Control Type, but is a Control Pattern w3c/aria#303 (1 comment by @joanmarie)
-
Core AAM: Ensure UIA mappings are correct for menuitemcheckbox and menuitemradio w3c/aria#615 (1 comment by @joanmarie)
-
CORE-AAM should suggest when to propagate readonly/editable state to gridcells w3c/aria#572 (1 comment by @joanmarie)
-
1 pull request opened in the SVG Accessibility Task Force.
-
1 pull request merged in the SVG Accessibility Task Force.
-
1 pull request in the SVG Accessibility Task Force received 2 new comments.
-
Core-AAM Issue 492: Clarify AX Tree Exclusion for Children Presentational True w3c/aria#647 (2 comments by @joanmarie, @mcking65)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
8 issues opened in the SVG Accessibility Task Force.
-
4.3 Text Alternative Computation (using placeholder attribute) w3c/aria#643, by @devarshipant.
-
Inconsistent text for role=spinbutton w3c/aria#642, by @ZoeBijl.
-
Missing role from aria-level definition w3c/aria#641, by @LJWatson.
-
Confusing Sentence for `aria-multiline` w3c/aria#631, by @cycomachead.
-
Consider the future of aria-flowto w3c/aria#630, by @cookiecrook.
-
Section 5.3.2 Widget Roles Inconsistence w3c/aria#621, by @JavierJF.
-
Core-AAM: Confirm MSAA/IA2 term role mapping w3c/aria#618, by @joanmarie.
-
Core-AAM: Confirm UIA term role mapping w3c/aria#617, by @joanmarie.
-
-
23 issues closed in the SVG Accessibility Task Force.
-
Section 5.3.2 Widget Roles Inconsistence w3c/aria#621.
-
Confusing Sentence for `aria-multiline` w3c/aria#631.
-
CORE-AAM 1.1: Create macOS mappings for aria-details w3c/aria#458.
-
CORE-AAM: need UIA mapping for aria-autocomplete w3c/aria#419.
-
Core AAM: Ensure UIA live region mappings are correct w3c/aria#614.
-
Core-AAM: Confirm UIA term role mapping w3c/aria#617.
-
Core-AAM: Confirm MSAA/IA2 term role mapping w3c/aria#618.
-
No CORE-AAM mapping for MSAA/IA2 of aria-pressed="mixed" w3c/aria#573.
-
No MSAA role mapping for switch role w3c/aria#600.
-
[CORE-AAM] application no longer a landmark w3c/aria#281.
-
CORE-AAM: clean up UIA mapping for aria-haspopup w3c/aria#428.
-
CORE-AAM: need UIA mapping for timer w3c/aria#418.
-
Replace mentions of primer with Authoring Practices w3c/aria#490.
-
-
29 issues in the SVG Accessibility Task Force received 83 new comments.
-
Consider the future of aria-flowto w3c/aria#630 (10 comments by @alice, @asurkov, @cookiecrook, @joanmarie, @LJWatson, @mcking65, @minorninth)
-
ARIA 1.1: aria-expanded is not supported on menuitem roles w3c/aria#454 (6 comments by @accdc, @joanmarie, @LaurenceRLewis, @mcking65)
-
CORE-AAM 1.1: Add mappings for aria-errormessage on macOS w3c/aria#457 (6 comments by @cookiecrook, @joanmarie)
-
CORE-AAM 1.1: Create macOS mappings for aria-details w3c/aria#458 (4 comments by @cookiecrook, @joanmarie)
-
CORE-AAM: UIA mapping for Link role should have value pattern w3c/aria#325 (4 comments by @boggydigital, @joanmarie)
-
Core-AAM: Add language regarding aria-setsize with a value of -1 w3c/aria#567 (4 comments by @asurkov, @joanmarie)
-
No CORE-AAM mapping for MSAA/IA2 of aria-pressed="mixed" w3c/aria#573 (4 comments by @asurkov, @joanmarie)
-
CORE-AAM should suggest when to propagate readonly/editable state to gridcells w3c/aria#572 (3 comments by @aleventhal, @joanmarie)
-
Core AAM: Ensure UIA mappings are correct for menuitemcheckbox and menuitemradio w3c/aria#615 (3 comments by @boggydigital, @joanmarie)
-
CORE-AAM: need UIA mapping for aria-autocomplete w3c/aria#419 (3 comments by @boggydigital, @joanmarie)
-
Core AAM: Ensure UIA live region mappings are correct w3c/aria#614 (3 comments by @boggydigital, @joanmarie)
-
SVG-AAM: Corrections to platform mappings for ATK w3c/aria#133 (2 comments by @AmeliaBR, @joanmarie)
-
SVG-AAM: Identify elements which support aria-roledescription without an explicit or implicit role w3c/aria#599 (2 comments by @AmeliaBR, @stes-acc)
-
CORE-AAM: cell mapping specifies TableItem as UIA Control Type, but is a Control Pattern w3c/aria#303 (1 comment by @boggydigital)
-
CORE-AAM Link Role mappings for MSAA+IAcessible2 need to update constant names w3c/aria#593 (1 comment by @joanmarie)
-
Core-AAM: Add additional requirements for aria-readonly for ATK w3c/aria#568 (1 comment by @joanmarie)
-
SVG-AAM: Consider explicit language regarding inclusion of elements with child title or desc w3c/aria#134 (1 comment by @AmeliaBR)
-
Core-AAM: Need to verify, expand upon, and/or correct AX API aria-activedescendant exposure w3c/aria#598 (1 comment by @joanmarie)
-
-
20 pull requests opened in the SVG Accessibility Task Force.
-
removed editorial note relating to issue522 w3c/aria#640, by @richschwer.
-
Add TableItem to role=cell mapping w3c/aria#638, by @boggydigital.
-
Add Selection CP to listbox widget role w3c/aria#637, by @boggydigital.
-
Remove SelectionPattern for role=list w3c/aria#636, by @boggydigital.
-
Add RangeValue CP to separator (focusable) w3c/aria#635, by @boggydigital.
-
Change Range CT to RangeValue CT w3c/aria#634, by @boggydigital.
-
Remove ValuePattern from link role w3c/aria#633, by @boggydigital.
-
Add LCT for cell, gridcell, row w3c/aria#632, by @boggydigital.
-
Proposal to add Bogdan Brinza (myself) to editors w3c/aria#629, by @boggydigital.
-
Update UIA mapping for role=term w3c/aria#628, by @boggydigital.
-
Update UIA mapping for aria-autocomplete=list, etc w3c/aria#627, by @boggydigital.
-
Update UIA mapping for role=timer w3c/aria#626, by @boggydigital.
-
Update UIA mapping for role=marquee w3c/aria#625, by @boggydigital.
-
Update UIA mapping for role=alert w3c/aria#624, by @boggydigital.
-
Update UIA mapping for role=cell w3c/aria#623, by @boggydigital.
-
Add ValuePattern to role=link w3c/aria#622, by @boggydigital.
-
Core-AAM: Add macOS mapping for aria-errormessage w3c/aria#620, by @joanmarie.
-
Core-AAM: Correct issues in aria-readonly mapping for MSAA/IA2: w3c/aria#619, by @joanmarie.
-
Update Practices references w3c/aria#616, by @joanmarie.
-
-
10 pull requests merged in the SVG Accessibility Task Force.
-
removed editorial note relating to issue522 w3c/aria#640.
-
modify 2F to process no role elements with content w3c/aria#611.
-
Update UIA mapping for role=cell w3c/aria#623.
-
Update UIA mapping for aria-autocomplete=list, etc w3c/aria#627.
-
Update UIA mapping for role=alert w3c/aria#624.
-
Update UIA mapping for role=marquee w3c/aria#625.
-
Update UIA mapping for role=timer w3c/aria#626.
-
Update UIA mapping for role=term w3c/aria#628.
-
Add ValuePattern to role=link w3c/aria#622.
-
Closes Tracker Issue 1049 w3c/aria#452.
-
-
12 pull requests closed in the SVG Accessibility Task Force.
-
Remove ValuePattern from link role w3c/aria#633.
-
Add TableItem to role=cell mapping w3c/aria#638.
-
Add LCT for cell, gridcell, row w3c/aria#632.
-
Add RangeValue CP to separator (focusable) w3c/aria#635.
-
Change Range CT to RangeValue CT w3c/aria#634.
-
Add Selection CP to listbox widget role w3c/aria#637.
-
Remove SelectionPattern for role=list w3c/aria#636.
-
Proposal to add Bogdan Brinza (myself) to editors w3c/aria#629.
-
Core-AAM: Add macOS mapping for aria-errormessage w3c/aria#620.
-
Updated aria examples, banner and contenting w3c/aria#358.
-
ARIA-PRACTICES in SpecRef w3c/aria#388.
-
19 pull requests in the SVG Accessibility Task Force received 42 new comments.
-
Core-AAM: Correct issues in aria-readonly mapping for MSAA/IA2: w3c/aria#619 (14 comments by @aleventhal, @asurkov, @joanmarie, @mcking65)
-
Core-AAM: Add macOS mapping for aria-errormessage w3c/aria#620 (6 comments by @cookiecrook, @joanmarie, @stes-acc)
-
modify 2F to process no role elements with content w3c/aria#611 (3 comments by @joanmarie, @richschwer)
-
Core-AAM: Remove LocalizedLandmarkType where there is semantic Landma… w3c/aria#639 (1 comment by @joanmarie)
-
ARIA 1.2: Add explicit guidance for non-pertinent errormessage elements (#587) w3c/aria#589 (1 comment by @joanmarie)
-
Lifecycle
-
1 charter started.
-
Chartered until 30 June 2018.
-
Participants
-
1 participant joined.
-
Liam Quin (W3C) joined.
-
GitHub
w3c/svgwg
-
5 issues opened.
-
CMYK Support w3c/svgwg#343, by @struddysit.
-
lengthAdjust values just for shrinking w3c/svgwg#341, by @Herst.
-
Verbose SVG for improved human readability w3c/svgwg#340, by @Crissov.
-
SVGElement.getBoundingClientRect(): which bounding box? w3c/svgwg#339, by @progers.
-
-
10 issues received 48 new comments.
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335 (10 comments by @fsoder, @fuchsia, @longsonr, @tshinnic)
-
Specify which attributes/properties are horizontal vs vertical vs other w3c/svgwg#211 (8 comments by @AmeliaBR, @BigBadaboom, @fsoder)
-
SVGElement.getBoundingClientRect(): which bounding box? w3c/svgwg#339 (6 comments by @AmeliaBR, @fsoder, @progers)
-
Compatibility mid-line rendering attribute to textPath w3c/svgwg#337 (5 comments by @fsoder, @msand)
-
Add a method to return the path direction (tangent) angle at a given distance w3c/svgwg#338 (5 comments by @BigBadaboom, @ewilligers, @karip)
-
Verbose SVG for improved human readability w3c/svgwg#340 (4 comments by @Crissov, @Herst, @longsonr, @struddysit)
-
Enhance `<pattern>` to support auto-width or auto-height for pattern tiles with a `viewBox` w3c/svgwg#342 (2 comments by @AmeliaBR, @fsoder)
-
TR publications
-
1 document published.
-
Motion Path Module Level 1 published as a Working Draft. History of Motion Path Module Level 1
-
GitHub
w3c/svgwg
-
9 issues opened.
-
Compatibility mid-line rendering attribute to textPath w3c/svgwg#337, by @msand.
-
Show need for "segment-completing closepath" with curves/arcs w3c/svgwg#336, by @tshinnic.
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335, by @fuchsia.
-
Shorthand properties should be promoted to presentation attributes. w3c/svgwg#334, by @BigBadaboom.
-
SVG marker orientation at a 180° U-turn not well defined w3c/svgwg#333, by @AmeliaBR.
-
Add `contenteditable` attribute for SVG text elements w3c/svgwg#332, by @AmeliaBR.
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331, by @tshinnic.
-
Contradiction in spec in regards to SVGUseElement.instanceRoot etc w3c/svgwg#330, by @BigBadaboom.
-
1 issue closed.
-
8 issues received 40 new comments.
-
SVG marker orientation at a 180° U-turn not well defined w3c/svgwg#333 (13 comments by @AmeliaBR, @BigBadaboom, @DavidBruchmann, @fsoder, @karip)
-
SVG2 path data coordinates are currently spec'd as integers. w3c/svgwg#335 (9 comments by @AmeliaBR, @fuchsia, @tshinnic)
-
Add a method to return the path direction (tangent) angle at a given distance w3c/svgwg#338 (8 comments by @AmeliaBR, @BigBadaboom, @fsoder, @karip)
-
Floating point number format discordance (SVG vs CSS vs browsers) w3c/svgwg#331 (4 comments by @DavidBruchmann, @longsonr, @tshinnic)
-
Shorthand properties should be promoted to presentation attributes. w3c/svgwg#334 (1 comment by @AmeliaBR)
-
Contradiction in spec in regards to SVGUseElement.instanceRoot etc w3c/svgwg#330 (1 comment by @AmeliaBR)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
8 issues opened in the SVG Accessibility Task Force.
-
Core AAM: Ensure UIA live region mappings are correct w3c/aria#614, by @joanmarie.
-
Remove links to ARIA Primer w3c/aria#603, by @detlevhfischer.
-
WCAG/ACCNAME discrepancy with `<img alt="" title="foo"> w3c/aria#602, by @cookiecrook.
-
No MSAA role mapping for switch role w3c/aria#600, by @jongund.
-
15 issues closed in the SVG Accessibility Task Force.
-
Core-AAM: Need to update mappings for aria-orientation w3c/aria#560.
-
CORE-AAM: UIA mapping for role=region w3c/aria#243.
-
Remove links to ARIA Primer w3c/aria#603.
-
CORE-AAM: UIA mapping for aria-rowspan w3c/aria#422.
-
-
21 issues in the SVG Accessibility Task Force received 25 new comments.
-
`aria-sort` forces `role="columnheader"` or `rowheader` Validation throws error on `<th>` w3c/aria#592 (3 comments by @DavidMacDonald, @hartman)
-
footer and header element context as landmarks (main element context change from parent to descendant) w3c/aria#362 (2 comments by @jasonkiss, @joanmarie)
-
ARIA 1.1: Determine if any features should be marked as "at-risk" w3c/aria#588 (2 comments by @joanmarie)
-
Core AAM: Ensure UIA mappings are correct for menuitemcheckbox and menuitemradio w3c/aria#615 (1 comment by @joanmarie)
-
Core AAM: Clarify expectations regarding implementation of IAccessible::accSelect() w3c/aria#612 (1 comment by @asurkov)
-
aria/aria.html#aria-live refers to "Section 5.2.1" of aria-practices, which does not exist w3c/aria#547 (1 comment by @joanmarie)
-
CORE-AAM: cell mapping specifies TableItem as UIA Control Type, but is a Control Pattern w3c/aria#303 (1 comment by @joanmarie)
-
CORE-AAM: AXRoleDescription for "contentinfo" should be "content information" w3c/aria#155 (1 comment by @joanmarie)
-
CORE-AAM: UIA mapping for Link role should have value pattern w3c/aria#325 (1 comment by @joanmarie)
-
[Core AAM] AXAPI exposure of buttons with a popup is not specified w3c/aria#539 (1 comment by @joanmarie)
-
Core-AAM: AXPress and AXShowMenu on aria-haspopup is potentially misleading/confusing w3c/aria#570 (1 comment by @joanmarie)
-
Core AAM: ATK mapping for searchbox and switch should include role as object attribute w3c/aria#597 (1 comment by @joanmarie)
-
ARIA 1.1: aria-expanded is not supported on menuitem roles w3c/aria#454 (1 comment by @sideshowbarker)
-
SVG-AAM: Identify elements which support aria-roledescription without an explicit or implicit role w3c/aria#599 (1 comment by @joanmarie)
-
-
9 pull requests opened in the SVG Accessibility Task Force.
-
modify 2F to process no role elements with content w3c/aria#611, by @richschwer.
-
Add aria-current mapping for values not in allowed list w3c/aria#610, by @richschwer.
-
Tooltipterm w3c/aria#608, by @richschwer.
-
Modify 2D for clarity/alignment with HTML AAM. w3c/aria#607, by @richschwer.
-
-
7 pull requests merged in the SVG Accessibility Task Force.
-
Add aria-current mapping for values not in allowed list w3c/aria#610.
-
Tooltipterm w3c/aria#608.
-
Modify 2D for clarity/alignment with HTML AAM. w3c/aria#607.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
5 pull requests in the SVG Accessibility Task Force received 13 new comments.
-
modify 2F to process no role elements with content w3c/aria#611 (5 comments by @joanmarie, @klown, @richschwer)
-
Editorial: Clarify the use of "undefined" as a literal value in the ARIA spec w3c/aria#609 (4 comments by @joanmarie, @richschwer)
-
Updated aria examples, banner and contenting w3c/aria#358 (2 comments by @brentonstrine, @joanmarie)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
11 issues opened in the SVG Accessibility Task Force.
-
Core-AAM: Definition role lacks platform role mapping for ATK w3c/aria#594, by @joanmarie.
-
Core AAM: Need to update IA2 mapping for aria-errormessage w3c/aria#591, by @joanmarie.
-
ARIA 1.1: Determine if any features should be marked as "at-risk" w3c/aria#588, by @joanmarie.
-
2 issues closed in the SVG Accessibility Task Force.
-
CORE-AAM 1.1: Implement feed role on macOS w3c/aria#456.
-
Minor nits in PR #446 w3c/aria#447.
-
-
11 issues in the SVG Accessibility Task Force received 16 new comments.
-
ARIA 1.1: aria-expanded is not supported on menuitem roles w3c/aria#454 (3 comments by @accdc, @jasonkiss, @joanmarie)
-
`aria-sort` forces `role="columnheader"` or `rowheader` Validation throws error on `<th>` w3c/aria#592 (2 comments by @hartman)
-
ARIA 1.1: Determine if any features should be marked as "at-risk" w3c/aria#588 (2 comments by @boggydigital, @joanmarie)
-
ARIA 1.2: Explicit guidance needed for non-pertinent errormessage elements w3c/aria#587 (2 comments by @joanmarie)
-
Core-AAM: Need to verify, expand upon, and/or correct AX API aria-activedescendant exposure w3c/aria#598 (1 comment by @cookiecrook)
-
Core-AAM: radiogroup should map to ATK_ROLE_PANEL; not ATK_ROLE_GROUPING w3c/aria#595 (1 comment by @joanmarie)
-
roledescription usage should not be limited to elements with defined ARIA roles w3c/aria#500 (1 comment by @cookiecrook)
-
-
4 pull requests opened in the SVG Accessibility Task Force.
-
Issue749 w3c/aria#585, by @richschwer.
-
7 pull requests merged in the SVG Accessibility Task Force.
-
Core-AAM: Update AX API mappings for feed role w3c/aria#578.
-
closes #447 w3c/aria#448.
-
Remove redundant sentence from paragraph w3c/aria#366.
-
ATK is in SpecRef w3c/aria#389.
-
Issue749 w3c/aria#585.
-
4 pull requests closed in the SVG Accessibility Task Force.
-
Remove redudant jQuery w3c/aria#393.
-
Remove redudant jQuery w3c/aria#392.
-
completed action 2070 w3c/aria#407.
-
AXAPI aready in SpecRef w3c/aria#390.
-
-
11 pull requests in the SVG Accessibility Task Force received 25 new comments.
-
ARIA 1.2: Add explicit guidance for non-pertinent errormessage elements (#587) w3c/aria#589 (10 comments by @asurkov, @joanmarie, @mcking65, @minorninth)
-
Added editorial examples for text alternative elements in the termino… w3c/aria#586 (4 comments by @joanmarie, @richschwer)
-
GitHub
w3c/svgwg
-
7 issues opened.
-
overflow="auto" should be treated as hidden rather than visible w3c/svgwg#329, by @longsonr.
-
SVGTransform's setMatrix method should take a DOMMatrix2DInit w3c/svgwg#326, by @zcorpan.
-
grammar for "closepath can substitute for final coordinate" is broken w3c/svgwg#325, by @tshinnic.
-
Remove un-implemented `pointer-events` "painted" rules for images w3c/svgwg#322, by @AmeliaBR.
-
-
7 issues received 28 new comments.
-
overflow="auto" should be treated as hidden rather than visible w3c/svgwg#329 (8 comments by @AmeliaBR, @DavidBruchmann, @tshinnic)
-
SVG MIME Type (image/svg+xml) is misleading to developers w3c/svgwg#266 (7 comments by @DavidBruchmann, @ghost)
-
SVG should specify what CSS attribute selectors and class selectors match on w3c/svgwg#328 (5 comments by @AmeliaBR, @bzbarsky, @tabatkins)
-
grammar for "closepath can substitute for final coordinate" is broken w3c/svgwg#325 (5 comments by @AmeliaBR, @nikosandronikos, @tshinnic)
-
Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec w3c/svgwg#309 (1 comment by @LoonyBean)
-
How does vector-effect=non-scaling-stroke interact with the stroke-dash* properties w3c/svgwg#323 (1 comment by @AmeliaBR)
-
-
1 pull request opened.
-
Use stretchy parentheses for the arctan argument. w3c/svgwg#327, by @fred-wang.
-
Participants
-
1 participant left.
-
Erik Dahlström (W3C Invited Experts) left.
-
GitHub
w3c/svgwg
-
8 issues opened.
-
Serialization format for path strings w3c/svgwg#321, by @ewilligers.
-
SVG and CSS transform w3c/svgwg#318, by @NtuFlorimond.
-
`text-anchor` not well specified for negative character advance w3c/svgwg#317, by @AmeliaBR.
-
Add a presentation attribute for `paint-order` w3c/svgwg#316, by @AmeliaBR.
-
Should support nomodule attribute on script elements w3c/svgwg#314, by @bzbarsky.
-
-
1 issue closed.
-
1 issue reopened.
-
8 issues received 19 new comments.
-
'd' presentation attribute inconsistent with shipped implementation and offset-path w3c/svgwg#320 (6 comments by @AmeliaBR, @ewilligers, @fsoder, @nikosandronikos, @shans)
-
Serialization format for path strings w3c/svgwg#321 (5 comments by @AmeliaBR, @BigBadaboom, @ewilligers, @tabatkins)
-
SVGAElement all attributes except href should be as HTML i.e. not SVGAnimatedString w3c/svgwg#315 (3 comments by @AmeliaBR, @longsonr)
-
Allow nesting filters instead of using 'in', 'in2' and 'result' attributes w3c/svgwg#258 (1 comment by @SebastianZ)
-
`text-anchor` not well specified for negative character advance w3c/svgwg#317 (1 comment by @fsoder)
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
5 issues opened in the SVG Accessibility Task Force.
-
Allowing `aria-hidden` on visible content excludes low vision uses w3c/aria#583, by @steverep.
-
aria-sort recommendation to have it only on ONE header w3c/aria#582, by @DavidMacDonald.
-
ARIA 1.1 has backwards-incompatible change for listitem names w3c/aria#581, by @aleventhal.
-
Issues with some pref/sref tags w3c/aria#580, by @LukeButters.
-
Issues with role: checkbox w3c/aria#579, by @LukeButters.
-
-
4 issues closed in the SVG Accessibility Task Force.
-
Issues with some pref/sref tags w3c/aria#580.
-
10 issues in the SVG Accessibility Task Force received 15 new comments.
-
aria-sort recommendation to have it only on ONE header w3c/aria#582 (2 comments by @hartman, @joanmarie)
-
[AccName AAM] reinforcing "name" vs "description", split out algorithm into two w3c/aria#544 (2 comments by @jechols, @patrickhlauke)
-
ARIA 1.1 has backwards-incompatible change for listitem names w3c/aria#581 (2 comments by @aleventhal, @joanmarie)
-
Core-AAM: Need to verify (and possibly correct) AXARIA{Column,Row}Index value w3c/aria#563 (2 comments by @joanmarie, @klown)
-
Allowing `aria-hidden` on visible content excludes low vision uses w3c/aria#583 (1 comment by @steverep)
-
-
1 pull request opened in the SVG Accessibility Task Force.
-
Core-AAM: Update AX API mappings for feed role w3c/aria#578, by @joanmarie.
-
-
1 pull request merged in the SVG Accessibility Task Force.
-
Update UIA landmarks mapping w3c/aria#576.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
19 issues opened in the SVG Accessibility Task Force.
-
role switch should have additional attribute aria-valuetext w3c/aria#574, by @stes-acc.
-
No CORE-AAM mapping for MSAA/IA2 of aria-pressed="mixed" w3c/aria#573, by @aleventhal.
-
DPub-AAM: UIA landmark mappings not consistent with Core AAM w3c/aria#571, by @joanmarie.
-
Core-AAM: Add additional requirements for aria-readonly for ATK w3c/aria#568, by @joanmarie.
-
Core-AAM: Add language regarding aria-setsize with a value of -1 w3c/aria#567, by @joanmarie.
-
typo in 7.4 Implicit WAI-ARIA Semantics w3c/aria#566, by @jasonkiss.
-
Core-AAM: Make Interface statements consistent for ATK/AT-SPI2 w3c/aria#565, by @joanmarie.
-
Core-AAM: Update AXRoleDescription for grid role for AXAPI w3c/aria#562, by @joanmarie.
-
Core-AAM: accessibilityIsAttributeSettable() is deprecated w3c/aria#561, by @joanmarie.
-
Core-AAM: Need to update mappings for aria-orientation w3c/aria#560, by @joanmarie.
-
role="row" needs to support aria-setsize, aria-posinset w3c/aria#558, by @aleventhal.
-
Inconsistency in rowgroup description w3c/aria#553, by @aleventhal.
-
-
6 issues closed in the SVG Accessibility Task Force.
-
typo in 7.4 Implicit WAI-ARIA Semantics w3c/aria#566.
-
1 issue reopened in the SVG Accessibility Task Force.
-
CORE-AAM 1.1: Implement feed role on macOS w3c/aria#456, by @cookiecrook.
-
-
18 issues in the SVG Accessibility Task Force received 45 new comments.
-
CORE-AAM 1.1: Implement feed role on macOS w3c/aria#456 (4 comments by @cookiecrook, @joanmarie, @mcking65)
-
Core-AAM: accessibilityIsAttributeSettable() is deprecated w3c/aria#561 (4 comments by @joanmarie, @klown)
-
Unnecessary and misleading role="tree" logic for role="row" mapping w3c/aria#554 (4 comments by @aleventhal, @klown, @mcking65)
-
role="row" needs to support aria-setsize, aria-posinset w3c/aria#558 (4 comments by @aleventhal, @jnurthen, @mcking65)
-
Core-AAM: Make Interface statements consistent for ATK/AT-SPI2 w3c/aria#565 (2 comments by @joanmarie, @klown)
-
Core-AAM: Update AXRoleDescription for grid role for AXAPI w3c/aria#562 (2 comments by @joanmarie, @klown)
-
DPub-AAM: UIA landmark mappings not consistent with Core AAM w3c/aria#571 (2 comments by @boggydigital)
-
[Core AAM] AXAPI exposure of buttons with a popup is not specified w3c/aria#539 (2 comments by @joanmarie)
-
Core-AAM: Need to verify (and possibly correct) AXARIA{Column,Row}Index value w3c/aria#563 (2 comments by @joanmarie, @klown)
-
Backwards-incompatible editorial change to grid/treegrid (was editable by default) w3c/aria#550 (1 comment by @aleventhal)
-
Core-AAM: AXPress and AXShowMenu on aria-haspopup is potentially misleading/confusing w3c/aria#570 (1 comment by @joanmarie)
-
[Core AAM] Update AXRoleDescription mappings for alertdialog and dialog w3c/aria#535 (1 comment by @joanmarie)
-
11 pull requests opened in the SVG Accessibility Task Force.
-
Add AXAPI mappings for button when aria-haspopup is not false w3c/aria#577, by @joanmarie.
-
Update UIA landmarks mapping w3c/aria#576, by @boggydigital.
-
Axapi popup button w3c/aria#575, by @joanmarie.
-
DPUB-AAM: Update mappings w3c/aria#564, by @joanmarie.
-
Core-AAM: Fix CFRange property names for AXAPI w3c/aria#557, by @joanmarie.
-
Core-AAM: Fix "current" state name for AXAPI w3c/aria#556, by @joanmarie.
-
Core-AAM: Fix AXRoleDescription value for tablist role w3c/aria#555, by @joanmarie.
-
Rewrite UIA introduction section w3c/aria#552, by @boggydigital.
-
Core-AAM: Correct spelling of two constants for ATK/AT-SPI2 w3c/aria#551, by @joanmarie.
-
DPUB-AAM: Map doc-pullquote for ATK, IA2, and UIA. w3c/aria#549, by @joanmarie.
-
Core-AAM: Update AXSubrole value for group role w3c/aria#548, by @joanmarie.
-
-
2 pull requests merged in the SVG Accessibility Task Force.
-
DPUB-AAM: Update mappings w3c/aria#564.
-
DPUB-AAM: Map doc-pullquote for ATK, IA2, and UIA. w3c/aria#549.
-
-
9 pull requests closed in the SVG Accessibility Task Force.
-
Axapi popup button w3c/aria#575.
-
Rewrite UIA introduction section w3c/aria#552.
-
Core-AAM: Fix "current" state name for AXAPI w3c/aria#556.
-
Core-AAM: Fix AXRoleDescription value for tablist role w3c/aria#555.
-
Core-AAM: Fix CFRange property names for AXAPI w3c/aria#557.
-
Core-AAM: Update AXSubrole value for group role w3c/aria#548.
-
Core AAM: Fix ATK/AT-SPI2 mapping for ARIA listitem role w3c/aria#545.
-
13 pull requests in the SVG Accessibility Task Force received 41 new comments.
-
DPUB-AAM: Map doc-pullquote for ATK, IA2, and UIA. w3c/aria#549 (3 comments by @joanmarie, @mattgarrish)
-
Add AXAPI mappings for button when aria-haspopup is not false w3c/aria#577 (2 comments by @joanmarie, @klown)
-
UIA changes to table of accessibility APIs for focus states and events w3c/aria#533 (1 comment by @boggydigital)
TR publications
-
1 document published.
-
CSS Fill and Stroke Module Level 3 published as a First Public Working Draft. History of CSS Fill and Stroke Module Level 3
-
GitHub
w3c/svgwg
-
2 issues opened.
-
SVGAElement implements two conflicting interfaces w3c/svgwg#312, by @saschanaz.
-
1 issue closed.
-
Remove SVGGeometryElement interface from <mesh>? w3c/svgwg#310.
-
-
11 issues received 21 new comments.
-
Add getScreenBBox() method to SVGGraphicsElement interface w3c/svgwg#76 (5 comments by @AmeliaBR, @fsoder, @jarek-foksa)
-
Remove SVGGeometryElement interface from <mesh>? w3c/svgwg#310 (2 comments by @AmeliaBR, @BigBadaboom)
-
getPathSegAtLength had consistent implementation behavior for invalid paths w3c/svgwg#313 (1 comment by @AmeliaBR)
-
Possible to use `<use xlink:href="#id">` in the presence of an HTML `<base>` element? w3c/svgwg#61 (1 comment by @longsonr)
-
GitHub
w3c/svgwg
-
1 issue opened.
-
Remove SVGGeometryElement interface from <mesh>? w3c/svgwg#310, by @BigBadaboom.
-
-
6 issues received 7 new comments.
-
Spec behavior of ::before and ::after within SVG text w3c/svgwg#125 (2 comments by @AmeliaBR, @nixkuroi)
-
Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec w3c/svgwg#309 (1 comment by @foolip)
-
-
1 pull request opened.
-
Change SVGMeshElement to derive from SVGGraphicsElement w3c/svgwg#311, by @BigBadaboom.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
10 issues opened in the SVG Accessibility Task Force.
-
Inserting content into live region vs turning on visibility w3c/aria#546, by @DavidMacDonald.
-
new attribute aria-readonly for role=form w3c/aria#542, by @stes-acc.
-
Author requirements clarification for aria-placeholder w3c/aria#541, by @feerrenrut.
-
I have to ask this question: role="logo" w3c/aria#540, by @ghost.
-
[Core AAM] AXAPI exposure of buttons with a popup is not specified w3c/aria#539, by @joanmarie.
-
accname-aam need to clarify aria-owns in Step 2F w3c/aria#538, by @jnurthen.
-
ARIA roles in ToC w3c/aria#534, by @marcoscaceres.
-
4 issues in the SVG Accessibility Task Force received 9 new comments.
-
I have to ask this question: role="logo" w3c/aria#540 (4 comments by @AmeliaBR, @ghost, @klown, @mcking65)
-
[AccName AAM] reinforcing "name" vs "description", split out algorithm into two w3c/aria#544 (3 comments by @jasonkiss, @patrickhlauke)
-
-
6 pull requests opened in the SVG Accessibility Task Force.
-
Core AAM: Fix ATK/AT-SPI2 mapping for ARIA listitem role w3c/aria#545, by @joanmarie.
-
Core-AAM: Fix error in IA2 and ATK mappings for aria-current w3c/aria#543, by @joanmarie.
-
Updated UIA mappings for role=heading w3c/aria#532, by @boggydigital.
-
-
2 pull requests merged in the SVG Accessibility Task Force.
-
Updated UIA mappings for role=heading w3c/aria#532.
-
3 pull requests closed in the SVG Accessibility Task Force.
-
5 pull requests in the SVG Accessibility Task Force received 13 new comments.
-
[Core AAM] Remove RELATION_POPUP_FOR from ATK/AT-SPI mappings of aria-haspopup w3c/aria#537 (4 comments by @joanmarie, @klown)
-
[Core AAM] Update AXRoleDescription mappings for alertdialog and dialog w3c/aria#536 (3 comments by @joanmarie, @klown)
-
UIA changes to table of accessibility APIs for focus states and events w3c/aria#533 (2 comments by @klown)
-
Participants
-
1 participant left.
-
Mark Sadecki (W3C Invited Experts) left.
-
GitHub
w3c/svgwg
-
5 issues opened.
-
Standardize SVGTests#requiredFeatures w3c/svgwg#308, by @LoonyBean.
-
SVG and CSS display:contents w3c/svgwg#305, by @ghost.
-
1 issue closed.
-
Standardize SVGTests#requiredFeatures w3c/svgwg#308.
-
-
3 issues received 4 new comments.
-
Include SVGGraphicsElement#farthestViewportElement and nearestViewportElement in the spec w3c/svgwg#309 (1 comment by @nikosandronikos)
-
1 pull request opened.
-
Remove explicit currentColor from <paint> w3c/svgwg#304, by @Manishearth.
-
SVG Accessibility Task Force
GitHub
w3c/aria
-
11 issues opened in the SVG Accessibility Task Force.
-
aria-controls should only point to visible elements w3c/aria#531, by @ZoeBijl.
-
Roles, states, and properties to support an accordion pattern w3c/aria#530, by @mcking65.
-
Role parity for html:blockquote, html:cite, html:q w3c/aria#528, by @cookiecrook.
-
Role parity for html:code, html:var, html:samp, html:kbd w3c/aria#527, by @cookiecrook.
-
Role parity for html:ins and html:del w3c/aria#526, by @cookiecrook.
-
[ROLE PARITY] "generic" role for div, span, br, etc. w3c/aria#525, by @cookiecrook.
-
Allow aria-setsize on container elements w3c/aria#524, by @mcking65.
-
Drag & Drop w3c/aria#521, by @michael-n-cooper.
-
fix role=directory MSAA mapping w3c/aria#520, by @asurkov.
-
-
2 issues closed in the SVG Accessibility Task Force.
-
Mac "AX" property and value names in AAM specs w3c/aria#399.
-
DPUB-AAM w3c/aria#444.
-
-
26 issues in the SVG Accessibility Task Force received 77 new comments.
-
ARIA 1.1: Remove children-presentational true from math role w3c/aria#425 (9 comments by @cookiecrook, @mcking65, @pkra)
-
Allow aria-setsize on container elements w3c/aria#524 (7 comments by @cookiecrook, @jessebeach, @jnurthen, @mcking65)
-
[ROLE PARITY] "generic" role for div, span, br, etc. w3c/aria#525 (5 comments by @cookiecrook, @mcking65)
-
Mac "AX" property and value names in AAM specs w3c/aria#399 (4 comments by @cookiecrook, @jasonkiss, @joanmarie)
-
Role Parity for semantically meaningless stylistic elements in HTML w3c/aria#485 (4 comments by @cookiecrook, @mcking65, @michael-n-cooper)
-
Radio Group should not have accessible name required: true w3c/aria#427 (2 comments by @cookiecrook, @mcking65)
-
aria-required vs required: spec mismatch between ARIA 1.1 and HTML 5.1 w3c/aria#433 (2 comments by @cookiecrook, @stevefaulkner)
-
Accessible name calc doesn't clearly say what happens with invalid reference or empty w3c/aria#515 (1 comment by @klown)
-
1 pull request opened in the SVG Accessibility Task Force.
-
ACTION-1732 w3c/aria#522, by @michael-n-cooper.
-
-
1 pull request closed in the SVG Accessibility Task Force.
-
ACTION-1732 w3c/aria#522.
-
-
1 pull request in the SVG Accessibility Task Force received 1 new comment.
SVG Accessibility Task Force
GitHub
w3c/aria
-
12 issues opened in the SVG Accessibility Task Force.
-
Document use cases for audio and video w3c/aria#518, by @michael-n-cooper.
-
Audio and video roles w3c/aria#517, by @michael-n-cooper.
-
Add identifies, defines, and indicates to the terms list. w3c/aria#516, by @cookiecrook.
-
CORE-AAM: Add conditional platform mappings for nameless forms w3c/aria#514, by @matatk.
-
Errors in section 5.3 "Categorization of Roles" w3c/aria#512, by @mcking65.
-
HTML br and wbr w3c/aria#510, by @michael-n-cooper.
-
HTML language directionality <bdi> and <bdo> w3c/aria#509, by @michael-n-cooper.
-
Figure out <mark> element w3c/aria#508, by @michael-n-cooper.
-
Figure out what the heck to do with the <time> element w3c/aria#507, by @michael-n-cooper.
-
5 issues closed in the SVG Accessibility Task Force.
-
Errors in section 5.3 "Categorization of Roles" w3c/aria#512.
-
12 issues in the SVG Accessibility Task Force received 35 new comments.
-
CORE-AAM 1.1: Add conditional platform mappings for nameless regions w3c/aria#513 (13 comments by @joanmarie, @klown, @matatk, @mcking65, @stevefaulkner)
-
CORE-AAM 1.1: Create macOS mappings for aria-details w3c/aria#458 (5 comments by @cookiecrook, @richschwer)
-
Accessible name calc doesn't clearly say what happens with invalid reference or empty w3c/aria#515 (3 comments by @klown, @mraccess77)
-
CORE-AAM 1.1: Create macOS Mappings for aria-colindex, -rowindex, -colcount, -rowcount w3c/aria#459 (3 comments by @cookiecrook, @joanmarie, @klown)
-
Role Parity for semantically meaningless stylistic elements in HTML w3c/aria#485 (1 comment by @michael-n-cooper)
-
[core-aam] Rule for excluding elements with children presentational true is out of date w3c/aria#493 (1 comment by @klown)
-
-
1 pull request opened in the SVG Accessibility Task Force.
Participants
-
1 participant left.
-
Doug Schepers (TPGi) left.
-
-
1 organization left.
-
Canon, Inc. left.
-
GitHub
w3c/svgwg
-
2 issues opened.
-
Make 'color-interpolation' work in associated alpha w3c/svgwg#303, by @leni536.
-
Support for 3D ancestor transforms in `getScreenCTM()` w3c/svgwg#302, by @BigBadaboom.
-
-
3 issues received 6 new comments.
-
Make 'color-interpolation' work in associated alpha w3c/svgwg#303 (2 comments by @leni536, @nikosandronikos)
-
SVG MIME Type (image/svg+xml) is misleading to developers w3c/svgwg#266 (2 comments by @co60ca, @paragonie-security)
-