W3C

– DRAFT –
ARIA Authoring Practices Task Force

16 March 2021

Attendees

Present
carmacleod, CurtBellew, jamesn, Jemma, jongund, MarkMccarthy, Matt_King, sarah_higley, ZoeBijl
Regrets
-
Chair
Matt King
Scribe
Jemma

Meeting minutes

APG github issue clean up for the transition - APG redesign project

<jamesn> /me we can still throw out some trash though right?

<jamesn> s/\/me we can still throw out some trash though right?//

Slider PR

https://github.com/w3c/aria-practices/wiki/March-16%2C-2021-Agenda

https://github.com/w3c/aria-practices/pull/1755

siri: non of screen reader seems not announce value max and min

jamesn: Yeah, and I wouldn't want to hear a screen reader doing it all the time reading the min and max value every time you focus in it because it seems like a lot of extra information that, yes, a visual user doesn't have to process, most of the time we just
 want to tweak a value

<MarkMccarthy> +1 jamesn

mck: can you comment the suggestions to ARIA AT project, Siri?

mck: if user is trying to go over max and min, alerting the user seems to be a good idea.

siri: I will file the issue.

checking review list of thumbslider

jamesn: I noticed an issue with it on Chrome, and Ed.

… I noticed an issue with it on Chrome, and Ed.

… those text elements in SVG are getting focused

jon: click event handler may give the focus.

sarah: The actual element that's being focused is the group which is even weirder.
… I don't see tab index

one with g tag is geting focused.

jamesn: f I inspect it and console and do a tab index on it. I just get minus one from it.

it is computed dom value

group is doing whether it is chrome bug or not for focus problem.

firefox and safari works fine

sarah: Why does it have focused on blur listeners?

jon: Oh, just so that when you hover over with the mouse with an outline around it, you know that they're active.


sarah: on blur listeners that are not supposed to be focused. I think we just took those off.

jon: I will take off the focus on blur listener.

another issue - https://github.com/w3c/aria-practices/pull/1755#pullrequestreview-613555583

mark: "Disapproving/requesting changes based on HCM Black w/ defaults not working in Firefox or Edgeium. On Firefox, only some text shows up. On Edgeium, nothing shows up. Screenshots to follow. HCM White w/ defaults works as expected."

jon: I mean, this current color thing is kind of tricky cuz the current color is really related to text, but we're using it an SVG.

car: I think you're using color current color but you probably have Excuse me, need to use filling stroke.

sarah: I had the same feeling

jon: I can look into it.

sarah: may be fill for text?

sarah: Windows high contrast mode won't override color used within an sVG. So if you want current color to update with high contrast mode color needs to be defined above it.

… Carolyn is right, the CSS attribute, or CSS property would need to be filled
… current color uses.
13:34:23

Whatever the Parent CSS color property is right.
… override color defined on the parent of the entire SVG

So if you have an SVG with multiple colors you can only have one color overridden by current colors

So, and it worked on Chrome I know, and so I don't. And so I'll have to go back and look at it seemed to work, it works in one mode of Firefox.


And when I looked at the dom specter on firefox. It said the text was supposed to be white, but it didn't render is white, it just wondered as black on black.


I'm not sure what that was about. I will look into it.

Plan file directory treeview updates for aria-at (Continued)

mck: I would like to focus on coming up with the simplest possible treview

at today

's meeting

mck: Or if we need to make any changes to the current computed file directory computed properties file directory tree view.

Do we need to make any changes to make it simpler other than like right now it doesn't currently use aria selected

And I think, at the end of the meeting we were saying that maybe we should add Aria selected there.

But are there any other changes are things that we could do to that example, to make it more simple more basic.


car: We need to add pointer event so that the example can work on touch device

mck: How do we make it seem kind of more understandable, as to what the point of the tree view is like here, you're selecting a value for a Purpose

and I don't know if the purpose in this case would be like to display the contents of a file but then in real life, you wouldn't want selection to follow focus.


car: when selection follows focus it updates right away and I think also, it should be on the right hand side, like side by side instead of up and down.


car: I guess there's checkbox trees, and they are sort of simpler except that they have checkboxes are usually for settings or options or something like that.
]

mck: hat's a perfect example for a multi select tree right would be settings thing. Yeah.


sarah: it might be useful to make to make the declared properties tree, the one we like heavily update and like check it out, get, like, virtualized maybe make it multi select to demonstrate how you do multi select.


mck: Tree behave differently in different implementations and so then I get nervous using them.

… I work around it
… It's like the point of the user interface is to choose a file to open. So you're choosing the file but you know until you have the Edit box which says, This is the file, you're going to open and as an open button.
 So you have like an edit box and open button and a tree.

mck: I am talking about use case of uploading the file to the web.

car: talking about complex implementation of those use cases
… a complicated dialogue and it does have a tree.

https://w3c.github.io/aria-practices/examples/treeview/treeview-1/treeview-1a.html

mck: If we're doing the simplest possible implementation should we specify Aria selected, or should we go with the new thing that we put into Aria 1.3 the language that allows the browser to set selecte

sarah: I think it'd be useful so something I see tree views, like relatively simple tree views, use for a lot is just like you have a file directory structure hierarchical structure so you have like a notepad like app except that, you know, rather than opening

… something, a file on your computer, because this is on the web, you have like a list of all your files within that web app on and then you can open any given one to edit the text within it, because let's say it's a text editing app like notepad or or

evernote.
… so the selected file is whatever is currently displayed in the main view on. And you definitely don't want that to file follow focus, so I see like that sort of thing a lot where you open like a panel like activating any item opens content in like

… a panel on, we could code that like it's very similar to our navigation patterns. Yeah, so it could like we could use essentially the same code or the same pattern where any, like, instead of having it populated edit box which I always assumed was just

… like a demonstration of, you click to thing rather than something realistic.


mck: So, in that case you're in that case you're proposing this would be a tree where selection does not follow focus. Right.

sarah: Unless you want to use like aria current or something but I think having that pattern be an example and demonstrating how you indicate which is the current item would be really valuable because a lot of people do that, and that's not reflected in any


of our examples currently.


mck: So, yeah, the way, are you selected is or the way, are you currently has written right now, you should actually use Aria selected for that. And the only reason we used current in the
 navigation tree view is because inside those three items they're actually links and what are your current, he pulls page was intended for specifically for navigation functions.


mck: I get the IDea here is selection, not following focus.
 If that was our simplest tree view example and as one where selection doesn't follow focus is, is that okay, like so.


sarah: personally I think windows deciding to have selection follow focus by default, has screwed us over in the present, and it was a terrible pattern.


mck: I guess my view is, as we try to make accessibility better on the web and with Aria in a one, one of my hopes is that we actually evolve the state of of screen readers and get them less dependent on legacy
 assumptions in the, with the aim of trying to make overall experiences simpler and easier to understand.


mck: The idea here would be, we have to write it up, put it in the issue, make sure people agree on. Essentially what the design is conceptually, and then we'll make the changes.

sarah: I'm happy to take on trees I would really like to make the declared properties tree into, like, an example where you would actually declare properties.

sarah will create the issue.

Action: Sarah will create the treeview design proposal

<trackbot> Created ACTION-2151 - Will create the treeview design proposal [on Sarah Higley - due 2021-03-23].

jemma: we can be ready for migration with APG redesign project by looking into open git hub issues. For an example, code example styling issues or mobile responsive design can be part of the first phase of project. We can also assign "site redesign" github issue label for these issues. Also "feedback" label will be one good place to see whether anything can be part of APG redsign projects.

resource: CSS at-rule: @media: forced-colors media feature https://caniuse.com/mdn-css_at-rules_media_forced-colors

Summary of action items

  1. Sarah will create the treeview design proposal
Minutes manually created (not a transcript), formatted by scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

Diagnostics

Failed: s/\/me we can still throw out some trash though right?//

Succeeded: s/period/parent

Succeeded: s/Topic: agenda label, site redesign/APG github issue clean up for the transition - APG redesign project

Maybe present: car, jon, mark, mck, resource, sarah, siri