Re: Grouping items in links
Re: Grouping items in links
- Subject: Re: Grouping items in links
- From: Daniel Göransson <email@hidden>
- Date: Sat, 05 Apr 2014 20:16:16 +0200
Hi all,
Yes this has been a very interesting discussion indeed, and could be wise to spread to a larger audience. ( And yep Ted, your understanding of y code is correct ;) )
To Chris' and Victor's points about plattform differences and if one or the other should be more/less granular; I believe that you can't expect one way of using a single device, as Pratik mentioned, you can use a Mac with a touch pad or or set VoiceOver cursor to follow mouse movement. (also other desktop OSs offer touch screen computability) and on iOS it is quite common for VoiceOVer users to use a keyboard or braille display to handle their device. My point is that the behavior should be the same regardless of device.
If it was standard that <a> elements functions as a group you could as a developer choose to pick it apart and go back to the current behavior by using role=link on the <a> element and wrap your block elements inside the link with <div role=link> (and yes it is valid to have block elements in a link as of HTML5) and on inline element use <span role=link>. This way we give developers the choice and don't have to use role=group which will change the semantic of the <a> element and to get the desired markup and function we would have to come up with something like aria-group="true".
(BTW, haven't post this as a feature request yet, is that recommended?)
Best regards
Daniel Göransson
Stockholm, Sweden
@DanielGoransson
5 apr 2014 kl. 00:16 skrev Victor Tsaran <email@hidden>:
> Ted,
> I don’t see why this shouldn’t be shared with a larger community. There are good points for discussion that should be out in the open.
> To add more spice to the soup, it is interesting to note that in native apps developers are allowed to group several items into single touchable objects, so why should websites be different?
> There is a case for both, flat view and an object navigation mode, so perhaps it should be a configuration setting of sorts?
>
> On Apr 4, 2014, at 2:02 PM, Drake, Ted <email@hidden> wrote:
>
>> Hi All
>>
>> I think this discussion has been fascinating, especially as it morphed
>> from how to accomplish a task to the philosophy of navigation between
>> mobile and desktop.
>> I put together a page with examples of the code snippets and summarized
>> the description. I thought it would be helpful to share with developers,
>> but wanted to make sure it was ok to share content from this mailing list.
>> I¹d also like to make sure I didn¹t mis-represent Daniel¹s code process.
>>
>> http://fyvr.net/a11y/block-level-links.html
>>
>> Would it be ok to publish this on my blog: last-child.com
>> <http://last-child.com>?
>>
>> Thanks
>> Ted
>>
>>
>>
>> On 4/4/14, 8:03 AM, "Pratik Patel" <email@hidden> wrote:
>>
>>> That's an excellent point, Marco. The touch pad is a much smaller
>>> surface. The UI is quite different. It makes sense. I do wonder though
>>> the direction of MacOS.
>>>
>>> -----Original Message-----
>>> From: Marco Zehe [mailto:email@hidden]
>>> Sent: Friday, April 04, 2014 10:22 AM
>>> To: Pratik Patel; 'Chris Fleizach'; 'Victor Tsaran'
>>> Cc: email@hidden
>>> Subject: Re: Grouping items in links
>>>
>>> Hi Pratik,
>>>
>>> On 4/4/2014 2:41 PM, Pratik Patel wrote:
>>>> Chris F wrote:
>>>> As Victor noted, iOS is much flatter than MacOS, so we want to give
>>>> individual access to each element within a link. Whereas, on the Mac,
>>>> you can navigate inside of that link group if you so desire.
>>>>
>>>> PP: With the touch pad being quite prevalent on most Macs in
>>>> circulation now, does this still stand for OS X?
>>>
>>> Yes, definitely. The touchpad requires you to interact (three finger
>>> swipe right) or stop interacting (three finger swipe left) with
>>> containers just like with the keyboard. The touchpad never shows the
>>> whole screen. So once you interact with an HTML content container, you
>>> only see the web content, and of that, usually only the stuff currently
>>> visible on the screen, and you have to three finger swipe up and down to
>>> scroll. You don't feel any of the browser's tool bars, the address bar
>>> etc., you have to stop interacting with the HTML content to get to those.
>>>
>>> Marco
>>>
>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Accessibility-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>> it.com
>>>
>>> This email sent to email@hidden
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden