"Accessibility"

Without knowing how this is addressed in other parts of the world, in the states we have something called the "Americans with Disabilities Act" or "ADA" which, in a nutshell,requires that certain website design/performance requirements be met for viewers who may be blind or deaf. I am fortunate to do some business with both federal and state entities here, and increasingly I am asked about "ADA compliance." In my research, there are two standards that go a long way toward meeting the ADA compliance requirements. One is that "Alt Tags" be available anytime there is a "transition element" like a hotspot, button, link, etc. Klaus has saved many of us a ton of headaches, time and....money by automating the various "tooltip" applications in KRPano - it is a most wonderful feature! The 2nd standard though is "tab navigation"....which could be expressed as the ability to move from "tooltip" to "tooltip" with the tab key. Is there a way to activate "Tab Key" navigation in a KRPano project? Here is a link with a generous number of "wayfinding" hotspots: http://www.photographyoptions.net/images/southark1/tour</a> How could one make "tab navigation" possible between scenes, and then, between hotspots in scenes? Thank you in advance!

Reggie

Thank you Umalo! I need to get better at finding solutions that are already plainly stated in the Documentation! I'm going to try and implement this and appreciate in advance your offer to help as I "stumble" through it!

Cheers, Reggie

It has been many years since I initiated this string. I was fortunate to interact directly with Umalo shortly after my first post and he generously supplied me with this code to try and enable the tab key navigation between scenes and "N" key navigation between hotspots within scenes:

<events name="tab" keep="true"
		
		onkeydown="
		if(keycode == '9', 	skin_nextscene_loop(+1));
		if(keycode == '78', hotspots_nexthotspot_n(+1));" 		
		
		onnewpano="set(newhotspotindex,-1);add(lasthotspotindex, get(hotspot.count), -1);"		
	 />
		
	<action name="hotspots_nexthotspot_n">
		add(newhotspotindex, newhotspotindex , %1);						
		if(newhotspotindex LT 0, copy(newhotspotindex,lasthotspotindex));
		if(newhotspotindex GT lasthotspotindex, set(newhotspotindex,0));		
		looktohotspot(get(hotspot[get(newhotspotindex)].name),get(view.fov));		
	</action>

	<action name="skin_nextscene_loop">
		add(newsceneindex, scene[get(xml.scene)].index, %1);
		sub(lastsceneindex, scene.count, 1);
		if(newsceneindex LT 0, copy(newsceneindex,lastsceneindex));
		if(newsceneindex GT lastsceneindex, set(newsceneindex,0));
		layer[skin_thumbs].scrolltocenter(get(scene[get(newsceneindex)].thumbx), get(scene[get(newsceneindex)].thumby));
		loadscene(get(scene[get(newsceneindex)].name),null,get(skin_settings.loadscene_flags),get(skin_settings.loadscene_blend));
	</action>

I tried to utilize this in one of my projects and it only partially worked. I used the free NVDA screen reader software to evaluate Umalo's adjusted accessibility feature in that tour....and joined the NVDA forum to learn more about how the visually impaired community feels about panoramic imagery in general. Having said this, I noticed when viewing the project in Microsoft Edge, the NVDA screen reader would (sometimes) pronounce in quick succession all of the scene titles that were in the thumbnail container.

If the focus of the tour could be programmed to automatically go to the thumbnail container....and then name off thumbs text in succession when using the screen reader....it might be the best place to start for providing accessibility to the projects I have created with KRPano.

I have looked at Google Street view images using the screen reader....and if there is a way to get it to read off the names of the street view scenes, I have not discovered it. How can I write an action that will steer initial focus to the text in the thumbnails so that it will name all of the scenes in the thumbs container from beginning to end...in all browsers? Are there any other ideas out there about how to make our tours more accessible to the visually impaired?