Protocols and Formats Working Group Teleconference -- 22 Jan 2015

<trackbot> Date: 22 January 2015

<richardschwerdtfeger> meeting: W3C WAI-PF ARIA Caucus

<richardschwerdtfeger> https://lists.w3.org/Archives/Public/public-pfwg/2015Jan/0116.html

<richardschwerdtfeger> https://lists.w3.org/Archives/Public/public-pfwg/2015Jan/0105.html

<jongund> The bridge won't let me in

<jongund> I am in now

<richardschwerdtfeger> scribenick: Rich

<clown> scribenick: richardschwerdtfeger

Action 1548 aria-current

<LJWatson> https://lists.w3.org/Archives/Member/w3c-wai-pf/2015JanMar/0015.html

<clown> action-1548?

<trackbot> action-1548 -- Léonie Watson to Write revised proposal for aria-current based on today’s meeting for issue 587 -- due 2015-01-08 -- OPEN

<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1548

<LJWatson> Aria-current attribute

<LJWatson> Indicates the element that represents the current item within a container or set of related elements.

<LJWatson> The aria-current attribute is an enumerated type. Any value not included in the list of allowed values must be treated by user agents as if the value true

<LJWatson> had been provided. If the attribute is not present or its value is an empty string, the default value of false applies and the aria-current state must

<LJWatson> not be exposed by user agents or assistive technologies.

<LJWatson> The aria-current attribute is used when an element within a set of related elements is visually styled to indicate it is the current item in the set. For

<LJWatson> example:

<LJWatson> The page token could be used to indicate a link within a set of pagination links, where the link is visually styled to represent the currently displayed

<LJWatson> page.

<LJWatson> The step token could be used to indicate a link within a step indicator for a step-based process, where the link is visually styled to represent the current

<LJWatson> step.

<LJWatson> The location token could be used to indicate the image that is visually highlighted as the current component of a flowchart.

<LJWatson> The date token could be used to indicate the current date within a calendar.

<LJWatson> The time token could be used to indicate the current time within a timetable.

<LJWatson> Note:

<LJWatson> The aria-current attribute is similar to the aria-selected attribute, but there are important differences. For example in a listbox widget for choosing

<LJWatson> between pages of search results, aria-current would be used to indicate the option representing the currently displayed page of results, Whereas aria-selected

<LJWatson> would be used to indicate the page of results the user had selected to be displayed next.

<LJWatson> Characteristics of aria-current

<LJWatson> Used in roles: All elements of the base markup.

<LJWatson> Value: token

<LJWatson> values of aria-current:

<LJWatson> page = Represents the current page within a set of pages.

<LJWatson> step = Represents the current step within a process.

<LJWatson> location = Represents the current location within an environment or context.

<LJWatson> date = Represents the current date within a collection of dates.

<LJWatson> time = Represents the current time within a set of times.

<LJWatson> true = Represents a current item within a set.

<LJWatson> false = Default.

Rich: This is fine. I think we can proceed to Joanie putting this in

<clown> +1

RESOLUTION: Accept Leonie’s proposal for aria-current and Joanie will take on the action item to put the aria-current text in the spec.

<joanie> For the record: I've transferred the action to myself with a due date of next week.

Jon: anything can do with a validator

group: no

scribenic: Leonie

<LJWatson> scribe: LJWatson

Action 1440

<clown> action-1440?

<trackbot> action-1440 -- Joanmarie Diggs to landmarks section uses "region of page" in prose even though "region" is not a landmark -- due 2015-01-22 -- OPEN

<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1440

Action-1440

<richardschwerdtfeger> http://rawgit.com/w3c/aria/1440/aria/aria.html#region

JMD: It's the whole 1440 branch that has been worked on.

MK: Landmark is abstract.

RS: On first pass think this looks pretty cool.
... One thing in landmark but not region... MK: Was doing most of the editing on this, after Joanie changed the hierarchy.

FE: It says "must have aria-label..."

MK: No, it's not a must.
... aria-labelledby is used to reference visible content, and I think that's better. I editorialised but didn't strike out stuff.

<richardschwerdtfeger> scribenick: Rich

<richardschwerdtfeger> Rich: aside from linking to section in region prose I though this was fine

<richardschwerdtfeger> Matt: one unique example. A region that included options for a data table. Above and below it, it says rows 15 to 1000, rows per page,

<richardschwerdtfeger> Matt: So, we had put a navigation region around it an labelled it results. It is exactly the same content above and below the table

<richardschwerdtfeger> Matt: It seems to violate a sensory perception rule

<richardschwerdtfeger> Matt: It mad it completely pointless

<richardschwerdtfeger> Matt: we have a navigation region labelled results. So, we have two regions having the same results. Both provide navigation have the same results above and below the table

<richardschwerdtfeger> Matt: the table was jut called results

<richardschwerdtfeger> Matt: you have results table and results navigation above and below the table

<richardschwerdtfeger> Matt: you can see that the navigation agenda is there above and below

<richardschwerdtfeger> Matt: giving them the same label is helpful

<richardschwerdtfeger> Matt: I thought about adding location information in the label was not helpful

<richardschwerdtfeger> Rich: that is a WCAG violation

<richardschwerdtfeger> Matt: results navigation located at the top of the table

<richardschwerdtfeger> joseph: is there an aria-controls?

<richardschwerdtfeger> Matt: the labels are not unique and we have a normative unique requirement.

<richardschwerdtfeger> Rich: if you take out unique then you make the testing a manual test

<richardschwerdtfeger> jamesn: left and right are generally ok but bottom and top are not

<jamesn> rich - that is the wrong way round

<richardschwerdtfeger> jamesn: correction: bottom and top are generally ok but left and right are

<richardschwerdtfeger> jamen: not

<clown> spelling mistake in landmark text at end of first paragraph: "by providing a dbrief, descriptive label". "brief" not "dbrief".

<Susann_Keohane> rich: if you have 2 at the same level with the same name that would be a potential problem

<Susann_Keohane> rich: my concern is that is will be a manual test

<mattking> An element with role region must have a unique label that describes the purpose of its content. Authors should reference a visible label with

<mattking> aria-labelledby

<mattking> if a visible label is present. Authors should include the label inside of a heading whenever possible. The heading may be an instance of the standard

<mattking> host language heading element or an instance of an element with role

<mattking> heading.

<clown> "An element with role region must have a label that describes the purpose of its content"

<Susann_Keohane> mattking: if you take the word unique out it doesn't change the testing requirements. With the work unique you have a manual test

<Susann_Keohane> mattking: w/o the word unique you still have the same manual test requirement

<Susann_Keohane> mattking: this is like link text, you have a unique requirement with the link labels. the manual test that the link describes it target

<Susann_Keohane> mattking: also like alt text, you must have alt text and it needs to be appropiate

<Susann_Keohane> jamesn: if you are only testing uniqueness you are fooling yourself you are testing requirement

<Susann_Keohane> rich: any manual test drives cost through the roof

<Susann_Keohane> mattking: unique label cause developers to make ugly labels to be unique

<Susann_Keohane> mattking: proposes that uniqueness not be in the verbiage

<Susann_Keohane> jamesn: rather flag it for developers to ensure they are doing the same thing if not there is a problem

<Susann_Keohane> rich: what's the groups decision

<jamesn> unique removed

<Susann_Keohane> fred: I would like to see unique removed

<richardschwerdtfeger> RESOLUTION: remove unique from region roles

<clown> issue-695

<trackbot> issue-695 -- Clean up nits in the ARIA specification -- raised