HTML Accessibility TF Zaragoza meeting 8-10 July 2015

We are fortunate to be hosted by the Ayuntamiento de Zaragoza - the city government - in the historic city of Zaragoza at their new ETOPIA centre.

Registration

PLEASE NOTE: If you are making a choice between this meeting or TPAC, we would prefer you attend the TPAC meeting

Please register whether attending remotely or in person.

Attendees should be members of the W3C HTML Working Group (instructions on joining).

Requests for "observer status", where you undertake not to propose any features which may be taken up in specifications may be granted by request to the Task Force coordinators.

Agenda

In development

The agenda will be developed somewhat "unconference style". People who are attending, or considering attending, should feel free to add requests to this section, including whether they plan to attend in person or remotely, whether this is conditional on their agenda being taken up, and whether there are timetabling constraints they would like respected.

We will endeavour to make the agenda match people's availability as far as possible. People can also contact the chair, or directly express ideas, positions, etc on the task force mailing list.

Timetables for each day are likely to consist of 6 approximately 1-hour formal sessions, with breaks between each. The timing is later than typical to match spanish meal schedules and facilitate remote participation from different time zones.

Topic requests

Wednesday

Making role attributes imply behaviour, to reduce the amount of javascript authors have to get right.

CMN (will be present):

DPub roles

CMN

Panels and Groups

JD,CMN

1. Stuff to discuss:
   1. Identifying the use cases
   2. Determining which role is appropriate for each use case identified
   3. Determining which roles (if any) should subclass panel
   4. Why does group have aria-activedescendant as a supported property? Should panel support it? Or does it really belong to neither and should be moved to a different class?
   5. Resolving/cleaning up some of the vague, hand-wavy stuff that is currently in the spec for group (the current content might be helpful in considering the first four items)
   6. Expected behavior of ATs wrt each role (might be helpful in considering first four items). A couple of examples which spring to my mind:
      1. Should ATs present the rolename for panel? What about group?
      2. Panels should always be presented. In the case of groups, the children / textual content should be presented of course. BUT what about the group itself?
   7. Implications for the ARIA role on the proposed panel element and vice versa (ideally we keep these things aligned, do we have sane mappings for the panel-related elements and their attributes?)
   8. Do we also want a panelset role? We have tablist (i.e. there's precedence) and the proposed panelset element (which has to map to something). Then again, we also have role explosion. We could potentially map the panelset element to the group role, and then make aria-multiselectable supported on group.
   9. Platform mappings
2. Related reading:
   1. https://www.w3.org/WAI/PF/Group/track/actions/1561
   2. https://specs.webplatform.org/common-panel/bkardell/gh-pages/
3. Intended outcome: A new branch of the ARIA spec with the new panel role, and any necessary changes to the group role, presented to the ARIA task force for consideration
4. Working branch for this face-to-face:
   1. https://rawgit.com/w3c/aria/zaragoza/aria/aria.html#panel
   2. https://rawgit.com/w3c/aria/zaragoza/aria/aria.html#group (note: At the time of this writing, group has not been modified at all; i.e., it's the current spec content)

ARIA "removable" attribute

JD

1. Stuff to discuss:
   1. Identifying the use cases (one of which happens to be the "removable" attribute of the proposed panel element).
   2. Determining which roles should support this new property
2. Intended outcome: IF we conclude this property would be desirable, a branch of the ARIA spec with the new property presented to the ARIA task force for consideration
3. Actual outcome:
   1. No strong opinions for or against aria-removable, but agreement it needs much more thought.
   2. In light of Léonie's explanation that this property exists in the panel element for the purpose of creating a dismiss control, agreement that the correct mapping for their property is "not mapped" in ARIA.
   3. Removed references to aria-readonly because they assumed aria-readonly could be applied to a parent container.
   4. Joanie will give this property some more thought but has no plans at this time to flesh it out or refine it further. And no one else is asking for it....
4. Working branch for this face-to-face: https://rawgit.com/w3c/aria/zaragoza/aria/aria.html#aria-removable

Should aria-readonly apply to more roles than it currently does?

JD

1. Stuff to discuss:
   1. aria-readonly strikes me as something which should apply to all inputs
   2. aria-readonly strikes me as something which may also be applicable on parent containers whose contents are normally directly user modifiable (including the proposed ARIA panel role)
2. Intended outcome: IF we conclude making these changes would be desirable, a branch of the ARIA spec with the changes presented to the ARIA task force for consideration
3. Actual outcome:
   1. General agreement that aria-readonly should indeed apply to other (most?) form field elements (Léonie disagrees).
   2. Consensus that Joanie's other proposals (turn aria-readonly into a true/false/undefined and then add it as a supported property of a parent container like the proposed panel role) were at best in need of more thought and much discussion.
   3. Creation of action-1678 and a new, action-specific branch in which aria-readonly was added to: combobox, listbox, radiogroup, slider, and spinbutton.
   4. Reopening of https://www.w3.org/Bugs/Public/show_bug.cgi?id=13390 so that this can be (re)considered for HTML5.
4. Working branch for this face-to-face: https://rawgit.com/w3c/aria/zaragoza/aria/aria.html#aria-readonly

Transcripts

CMN What are the aria implications for interactive transcripts?

agreement that there are no obvious ones.

Thursday / Friday

Custom elements and accessibility issues

CMN

Interaction behaviours

CMN This covers how people work with various kinds of interface and content today, in HTML, SVG, and other applications, and how they interact using different kinds of physical interface. So it's not a small project.

Date pickers

CMN there are many problems with deployed date pickers and accessibility, and the HTML5 input type=date basically didn't manage to solve them. What now?

Wednesday 8 July

ARIA topics

1. 10 - 11
2. 11.30 - 12.30
3. 13 - 14
4. LUNCH
5. 15.30 - 16.30
6. 17 - 18
7. 18.30 - 19.30

Thursday 9 July

1. 10 - 11
2. 11.30 - 12.30
3. 13 - 14
4. LUNCH
5. 15.30 - 16.30
6. 17 - 18
7. 18.30 - 19.30

Friday 10 July

1. 10 - 11
2. 11.30 - 12.30
3. 13 - 14
4. LUNCH
5. 15.30 - 16.30
6. 17 - 18
7. 18.30 - 19.30

Logistics

Remote participation

Remote participation is possible through our normal irc channel, and on request a webex meeting. The meeting codes are 317 944 342 and f2f but you should connect to IRC and ask us to connect to webex

Venue

We are hosted through the kindness of the Ayuntamiento de Zaragoza (Zaragoza city government), a long-standing member of W3C, at the ETOPIA centre (in spanish) - english via Yandex translate.

The address is Avenida Ciudad de Soria 8, Zaragoza, Aragon, Spain

Getting there

Zaragoza has an airport, but there are very few international flights. Most of them are operated by RyanAir from european airports. Far more effective for most people will be to fly to either Madrid or Barcelona, and take an AVE (fast train - an hour and a bit from central train stations in each city) or a bus (several hours, but leaving regularly direct from Madrid airport - I'll check about Barcelona).

trains

RENFE is the national train operator, and run trains from both Barcelona and Madrid to Zaragoza (it's roughly in the middle). If you have difficulty with their website, please feel free to contact chaals.

Tickets are between €20 and €70 one way, and the journey is about one and a half hours. Trains depart from Barcelona Sants, or Madrid Atocha - both reachable by public transport (for a few euros) or taxi (for €20-30) from the respective airports.

The venue is very close to the train station, connected by a walkway.

Buses

Buses direct from Madrid airport (Terminal 4) to Zaragoza run every hour or so, cost €30 - €60 round trip depending on class, and take between three and a half and four hours.

Bookings can be made online directly with [Alsa].

Supra buses are more expensive, have bigger "business class" seats, (not very fast) wifi, and snack/drink service like on a plane. Supra economy has the nice seats, but without the beer and chips.

Shared rides / Driving

Car rental is simple, but check that your license is valid (European licenses are, Australian licenses aren't unless you have an international driving permit…).

Having a car in Zaragoza itself is pretty pointless as the city is small, walkable, mostly flat, and unfriendly for driving. Plus there is good public transport and taxi service. But if you want to get out on the weekend a car can be useful. Zaragoza is on the A2 freeway that connects Barcelona to Madrid - driving from Madrid there is one toll section, driving from Barcelona there are more. In either case the distance is 300km and will take about 3 1/2 hours plus rest breaks.

It is also possible to look for a shared ride at BlaBlaCar but I have never tried it and would recommend normal precautions about taking a ride from someone you don't know.

Staying There

Free accommodation is available at the Etopia centre for registered attendees in standard hotel-style rooms. If you would like to book one, please contact chaals.

Zaragoza is a lovely historic city, and there are many options for cheap accommodation within an easy walk or bus ride of the venue.