{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Explosion°爆炸 的问题《How to define screen reader sequence for a web pag》','https://www.manongdao.com/q-907349.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm working on an accessibility task for a mobile web app (HTML+Angular+ARIA). I tested some potential ways:
aria-flowtoandaria-owns, not working for web pagetabIndex, not working
In my local test with iOS 9.2.1 Safari, the default screen reader is linear way from top. Is there a way I can define elements reading order? Like what aria-flowto is doing.
aria-flowtois supposed to provide this sort of functionality (and it is the only proposed way to do so) but it has not been implemented yet by AT vendors (or by browsers for keyboard-only access).As such, the only thing you can do is to ensure that the order of the elements in the DOM is the order that is natural for a screen reader to read the page.