Re: Draft talk Maps for the Web Workshop

Hi Josh,

I will try to answer best as I can.
My idea was to highlight requirements for an accessible Web Map HTML native element, using current semantics and available “tools” (e.g. ARIA).
As one of the aims of the workshop is to define a Web Map HTML native element, I think that can be interesting to start with “how can we make it accessible with the tools we already have?” and possibly, from that, discuss and try to understand if they are enough. Talking more practically, a ‘user needs and requirements’ list like the one used on the XAUR, for example https://www.w3.org/TR/xaur/#xr-user-needs-and-requirements <https://www.w3.org/TR/xaur/#xr-user-needs-and-requirements>

I was not thinking to give a Demo, as we do not have the map HTML element. I think that at this stage it can be interesting to “just” highlight user needs and requirements without going to implement some non-standard solution.

The idea to integrate other APA specs is great, but I will need a bit of help with it. Maybe the integration will be easier to spot with the complete proposal? Then we can show needs and requirements to other APA members that knows all possible integrations better than me.

Hope this makes sense, let me know

Thank you

Nicolò Carpignoli

Chialab Design Company
via Arrigo Lucchini 9
40134 Bologna, Italy
+39 0516154398 int. 507
www.chialab.it <https://www.chialab.it/>

> Il giorno 10 ago 2020, alle ore 16:58, Joshue O Connor <joconnor@w3.org> ha scritto:
> 
> Hi Nicolò,
> 
> I'm just back from holidays myself and want to bounce some thoughts relating to your suggestion below.
> 
> I'm wondering how we can tie this into a general thread around the need for improved semantics? Or do you feel it is sufficient to demonstrate what can be currently done with ARIA/HTML and other meta data?
> 
> Some other thoughts:
> Should we explicitly frame the talk proposal in the context of current semantic limitations from an a11y perspective? I'm not saying we should btw, and am genuinely asking the question.
> Will your presentation demo the use of particular polyfills? Or the need to support some kind of brittle plug in architecture to build accessible map implementations?
> Are there other current APA specs or works in progress, such as Personalisation or Pronunciation that we could demonstrate here also?
> Apologies if that sounds like too much ground to cover (likely is) but these thoughts came to me when reviewing this.
> 
> Thoughts?
> 
> Thanks
> 
> Josh
> 
> 
> Nicolò Carpignoli wrote on 23/07/2020 11:26:
>> 
>> Hi everybody,
>> 
>> I attach a first draft of my proposal for a talk for the Maps for the Web Workshop (https://www.w3.org/2020/maps/ <https://www.w3.org/2020/maps/>).
>> Following what we discuss on last RQTF meeting (https://www.w3.org/2020/07/22-rqtf-minutes.html <https://www.w3.org/2020/07/22-rqtf-minutes.html>), I have written two paragraphs highlighting some user-cases/requirements
>> about the need for annotations on 2D map on the Web for a11y purposes.
>> 
>> Please feel free to review and eventually fix/add mistakes or comment about what’s missing:
>> 
>> From an accessibility perspective, to create accessible Web map experiences that adapt to the different ways people interact with the Web means to take in account several aspects.
>> One of them is about the need for annotations of geolocated data and maps metadata. Once those annotations are specified and then delivered by the technologies, they become available to be used from non-visual outputs such as Speech Synthesis. Maps are used everyday by users to know information about places, routes and to navigate towards locations.
>> Maps can be either complex or simple, can show a lot of information or few. According to the user needs, maps are often configurable and users switch to different views for the same data.
>> 
>> Several accessibility related use-cases will be showed with requirements to solve them. Some examples: 
>> - a wheelchair user wants to know about wheelchair paths on the current map
>> - a pedestrian needs to know a path available to reach a specific place safely by feet
>>  A possible solution to the needs above can be to provide a contextual menu to switch between different views of the same map/area.
>> - a blind user needs to hear about the current map size, the boundaries and possibly move the map to highlight a different area
>>  The boundaries of the map can be read aloud by the Speech Synthesis tool as those information are provided on the screen as text, as well as the extension of the map currently showed
>>  on the screen. Four HTML buttons can be provided to move the map and change the zoom level to navigate the area, and look for new data.
>> - users should be able to change the map unit according to their needs (meters, kilometres, foots, miles, etc.)
>>  People from different countries are comfortable with specific units and can found problems in reading the map with different units.
>> - A blind user wants to navigate the map without feeling frustrated and loose too much time in moving the selected area.
>>  Map scale is fundamental to have an idea about the extension of the area currently shown on the map. Scale (that can be unified with the idea of ‘zoom’ level) should be available as a text annotation.
>> More example will be highlighted during the talk.
>> 
>> 
>> Please let me know about:
>> - content
>> - the detail level (too much detail? or too general?)
>> - text form
>> 
>> I will be available for modifies until Monday 27 then I will be away two weeks.
>> 
>> 
>> 
>> Nicolò Carpignoli
>> 
>> Chialab Design Company
>> via Arrigo Lucchini 9
>> 40134 Bologna, Italy
>> +39 0516154398 int. 507
>> www.chialab.it <https://www.chialab.it/>
> 
> 
> -- 
> Emerging Web Technology Specialist/Accessibility (WAI/W3C)