- From: Peter Rushforth via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Jul 2021 17:33:35 +0000
- To: public-sdwig@w3.org
@cperey: > we haven't had much discussion of visualisation, which I see as missing from this list. Not just accessible on the web but also visible to people re: visualization rendered maps are accessible information for sighted individuals, depending on the disability. Christine is correct that we can't really start a discussion of accessible spatial information without first talking about rendered, visual maps. We need to build accessibility into our discussion from the outset, however, because you can't tack it on after the fact. As @lieberjosh pointed out at last year's [workshop](https://www.w3.org/2020/maps/report): > There really is a continuum… between a flat map oriented north with a fixed extent and scale and… augmented reality where you really are looking at what’s around you and in front of you and having map objects placed into that view. … [A] Web Map that… is able to transition from… augmented reality to [a] mapped formalism of reality… can really be put into this spectrum…. GeoPose is an important part of establishing that continuum. Not only is there a continuum between 2D Web maps and an augmented reality, but there is a continuum of accessibility for individuals of all abilities -> disabilities. We need to make our outcomes work across the continuums. A critical first step in this direction is to get the browser engine, **which renders content for visualization**, to "understand" the particularities of geospatial coordinate reference systems*, which are involved in everything from 2D Web maps, to processing geofences, to augmented reality. To accomplish that (which is at first a social problem, and once properly socialized, a highly technically specialized problem of a different nature), one needs a highly cogent argument for including "maps" in HTML. And that argument needs to be based on and start with accessibility and inclusivity. So this is the nature of the problem domain that we are working on in the maps for HTML community, and we are looking for shared objectives and partners and contributors. Happy to "merge" [2], with the SDWIG if we can agree on objectives. * as applied on the Web. Which might mean less today that it one day certainly will, because the Web should always "win". [2] I can't speak for everybody and we so far have a 100% public community group, but anyway, we'll work with any self-identified people and organizations who want to work with us. So maybe "work alongside and report into" would be a better approach than "merge", but you get the idea. -- GitHub Notification of comment by prushforth Please view or discuss this issue at https://github.com/w3c/sdw/issues/1271#issuecomment-885089433 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 July 2021 17:33:37 UTC