- From: Cameron Jones <cmhjones@gmail.com>
- Date: Wed, 16 Oct 2013 16:19:27 +0100
- To: Steve Faulkner <faulkner.steve@gmail.com>
- Cc: Willem-Siebe Spoelstra <info@spoelstra.ws>, HTMLWG WG <public-html@w3.org>
- Message-ID: <CALGrgevC5iYvprH0WB_Jy45GZAyYqrqZOMm0qcjqpGqp5eraJQ@mail.gmail.com>
On Wed, Oct 16, 2013 at 4:13 PM, Steve Faulkner <faulkner.steve@gmail.com>wrote: > > On 16 October 2013 16:08, Cameron Jones <cmhjones@gmail.com> wrote: > >> On Wed, Oct 16, 2013 at 2:56 PM, Steve Faulkner <faulkner.steve@gmail.com >> > wrote: >> >>> >>>> 3) The arrows should not be content but CSS in my opinion. >>>> >>> >>> the arrows convey direction to sighted users and I think they should >>> also convey direction to other users too, having them in text means that >>> they are announced by AT for example. NVDA announces: (→ "right arrow") >>> >>> list with 4 items >>> You are here: >>> link >>> Main >>> → >>> link >>> Products >>> → >>> link >>> Dishwashers >>> → >>> Second hand >>> >>> >> Is this really a good idea? Isn't this the same problem of mixing style >> with structure? >> > > ? the arrows have a meaning that meaning is conveyed regardless of style. > Only within the context of the set of breadcrumbs. If the set of breadcrumbs is already defined, then the arrows are noise. > >> The style isn't a graphical style, but an auditory style. >> >> If aria roles are used to markup the breadcrumbs and then isn't the >> screen reader able to describe the content in the appropriate fashion? >> > > there is no role=breadcrumbs > Hmm...i would have thought this was an ideal candidate for a role="" > >> <nav role="breadcrumbs"> >> <ol>...</ol> >> </nav> >> >> So, the announcement would be: >> >> "breadcrumb navigation" >> "list with 4 items" >> ... >> >> Seems better than requiring some plaintext construct to markup a list of >> links. >> > > where plain text does the job well why not use it? > Because it isn't very semantic Thanks, Cameron Jones
Received on Wednesday, 16 October 2013 15:19:54 UTC