- From: T.V Raman <raman@google.com>
- Date: Mon, 16 Mar 2015 09:33:40 -0700
- To: guha@google.com
- Cc: chaals@yandex-team.ru, raman@google.com, lwatson@paciellogroup.com, public-vocabs@w3.org
1+ on going breadth-first here. In addition to the coverage issues you point out, going super-detailed will: A. Make the vocabulary hard to use -- B. (A) will lead to inconsistencies in usage and C: A, B together will mean there is insufficient data to aggregate along any given axis. Guha writes: > There is a meta-issue that needs to be resolved --- we can create a super detailed vocabulary that covers everything (height of wash basin, steps to bathroom, ...), but it > is useful only if a substantial number of establishments are covered (i.e., described using this vocabulary on some website). > > I am very wary of a super detailed vocabulary. We are unlikely to both converge on such a vocabulary and even less likely to gain widespread adoption (amongst publishers and > applications) of such a detailed vocabulary. > > I propose that we start with something comparatively simple, in core schema.org, while at the same time, the domain experts can create an extension (accessibility.schema.org > ) that does indeed go into the level of detail discussed in this thread. > > guha > > On Fri, Mar 13, 2015 at 4:35 AM, <chaals@yandex-team.ru> wrote: > > 12.03.2015, 00:36, "Guha" <guha@google.com>: > > Chaals, Leonie, > > This is absolutely great. How do we get from here to a vocabulary? > > > I think "slowly and organically, at least to begin with". There are obviously a ton of things that people might need to know, but equally obviosuly there are a ton of > people who will need to use the vocabulary, and whose understanding of the issue is pretty minimal - of the variety "sure, I have a ramp at the door, or only a tiny step > I can get my trolley over, so I'm good, right?" > > I'd like to start with a couple of things really fast, adding more (or fixing things we did) as we get experience. > > A useful thing I think most people could get right might be > wheelChairEntry > whether there is an entry suitable for a 'standard-size' wheelchair (at least 95cm/34" wide, no steps). > Enumeration: "main", "none", "separate" > > I'd like to have something like "accessibilityNotes" that is a URL or text, effectively providing a pointer to something elsewhere, and enabling people to tell a more > complete story without having a complete supporting vocabulary. This is actually a common thing on websites, so should apply to CreativeWork as well as Place. > > Contact details are a useful thing if people have questions that aren't answered by the information posted. They are actually already there, but if we are describing the > things we do for physical accessibility we should note that. Likewise things like online or braille menus should be covered by the CreativeWork stuff, but we should > point that out in describing the topic. > > Parking for disabled people is tricky. Geographic information is pretty complicated and really a more general problem, and parking for disabled people has its own set of > issues we may want to delve into - or not. So I am going to start thinking about it, without proposing anything yet. > > We should probably start collecting the things we have into a wiki… > > cheers > > > > > guha > > On Tue, Mar 10, 2015 at 3:43 PM, Léonie Watson <lwatson@paciellogroup.com> wrote: > > > From: chaals@yandex-team.ru [mailto:chaals@yandex-team..ru] > > Sent: 10 March 2015 05:16 > > there are lots of things that people might want to know about in regards to > > accessing a physical place (restaurant, bar, stadium, government office, etc.). > > Some things people will want to know will be general to all environments, whilst others will be specific to certain types of environment. The following > suggestions don't fall into any particular grouping though... > > Is the main entrance wide enough to be usable with a wheelchair? > Is there an alternative entrance that is wide enough to be usable with a wheelchair? > What is the location of the doorbell/buzzer at the main entrance? > Are corridors (including corners) wide enough to be navigated with a wheelchair? > Can electric/power sockets be reached from a sitting position? > Where are the electric/power sockets? > Can light switches be reached from a sitting position? > Can wash basins, kitchen facilities etc. be used from a sitting position? > Can lift/elevator buttons be reached from a sitting position? > Does the lift/elevator announce each floor with speech? > Does the lift/elevator have braille labels for buttons? > Does the lift/elevator have tactile buttons? > Does the lift/elevator have high-visibility buttons? > Is there adequate space for wheelchairs in meeting spaces, auditoriums, dining rooms etc.? > Is the reception desk/registration point wheelchair friendly? > IIs the bar wheelchair friendly? > Is there table service? > Is the environment free of obstacles at ground-level? > Is the environment free of obstacles at head-height? > Is there a place where guide dogs (and other service animals) can be fed/watered/relieved? > What is the route from the main entrance to the place where guide dogs can be fed/watered/relieved? > Are there parking spaces for people with disabilities? > How many parking spaces for disabled people are available? > How far from the main entrance of the building are the parking spaces for disabled people? > Does the emergency system issue both audible and visual signals? > Is there a hearing loop/assisted listening system available? > Do signs and signage have high visibility? > What is the route from the main entrance to X (where X might be the bar, reception, restroom etc.)? > Do air-con controls have tactile buttons/speech output? > > Undoubtedly lots more that should be added, but that's all I can think of for the moment without getting into some questions that are very specific to certain > types of environment. If these would be useful in any case, let me know though. > > Léonie. > > -- > Senior Accessibility Engineer, TPG > @LeonieWatson @PacielloGroup > > > > -- > Charles McCathie Nevile - web standards - CTO Office, Yandex > chaals@yandex-team.ru - - - Find more at http://yandex.com > > -- --
Received on Monday, 16 March 2015 16:34:08 UTC