RE: Urgent: design decision for presenting related linkson example pages

Siri, what do you mean? A heading that labels the four links? Something like
"Related Links"? Do others think that would be helpful? I am not very sure
about it.

 

I didn't include github in the labels because I was worried about the length
of text and wasn't sure that it really added information that would help the
user decide whether to activate the link. 

 

The information I omitted with less confidence was using "AT" instead of
"Assistive Technology". I don't really like having that abbrefiation there.
Similarly, I left the name of the design pattern out of the design pattern
link, e.g., "Design Pattern" instead of "Accordion Design Pattern". I am
hoping the design pattern target is adequately implied by the page title.
So, if we were to add more words to the link text, I would be inclined to
lengthen one of those.

Matt

 

From: Balusani, Shirisha [mailto:sirib@uillinois.edu] 
Sent: Wednesday, November 29, 2017 11:30 AM
To: Ku, Jaeun <jku@illinois.edu>; James Nurthen <james.nurthen@oracle.com>;
public-aria-practices@w3.org
Subject: RE: Urgent: design decision for presenting related linkson example
pages

 

Hi Matt and James,

I  like the accordion example but can you please add a heading to it.

Also, can you make "Report issue" & "Related issue" links more meaningful by
adding "Report Issue via Github" and "Related Issues in GitHub"?

 

In the alert example, the user is not notified if the accordion is expanded
or closed.

 

Thanks,

Siri

 

 

 

From: Ku, Jaeun [mailto:jku@illinois.edu] 
Sent: Wednesday, November 29, 2017 10:47 AM
To: James Nurthen <james.nurthen@oracle.com
<mailto:james.nurthen@oracle.com> >; public-aria-practices@w3.org
<mailto:public-aria-practices@w3.org> 
Subject: RE: Urgent: design decision for presenting related linkson example
pages

 

I think that would work. 

By the way, I had a second thought about my claim on Nav(because I see <nav>
tag). Actually, they're "related links" as James grouped them, not
navigation items  in the page/site.

I think I was wrong about calling them as navigation items. 

 

Thanks again, James and Matt.

 

Jemma

 

From: James Nurthen [mailto:james.nurthen@oracle.com] 
Sent: Wednesday, November 29, 2017 10:36 AM
To: public-aria-practices@w3.org <mailto:public-aria-practices@w3.org> 
Subject: Re: Urgent: design decision for presenting related linkson example
pages

 

If people prefer them simply inline at the top of the example then we can do
that.

 

On 11/29/2017 7:54 AM, Ku, Jaeun wrote:

Thanks for working on this, Matt and James.

 

If I have to vote for one, I will choose the accordion example, which saves
one more click and show all the links at once. 

The benefit of this design is good for mobile but user may miss these links
like I did because links are is in the fixed position on top right corner.
(people tends to read from left to right)

 

If you two are willing to go further, how about making this as horizontal
list under the heading 1(design pattern name) since they are navigation
items anyway for all the example pages? 

We just need to put display style as inline for li items in nav ul. 

 

What do you think?

Jemma

 

 

From: Matt King [mailto:a11ythinker@gmail.com] 
Sent: Wednesday, November 29, 2017 2:41 AM
To: public-aria-practices@w3.org <mailto:public-aria-practices@w3.org> 
Subject: Urgent: design decision for presenting related linkson example
pages

 

All,

 

For issue 536, we are adding four links to the top of each example page.
James and I have two options for you to consider. Please look at:

 

Option 1:
https://rawgit.com/w3c/aria-practices/example_nav/examples/accordion/accordi
on.html
<https://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_aria-2D
practices_example-5Fnav_examples_accordion_accordion.html&d=DwMFAg&c=RoP1Yum
CXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6v
e6hP0I&m=ASWss0GwB5diPwJ9Po7t5FpvV7tK4G3AltcNiUPEngU&s=9U0HLwx1hrm_HCmML5C3G
bGaOX9GDqdXim17N6vS0bs&e=> 

 

Option 2: https://rawgit.com/w3c/aria-practices/example_nav/examples/alert/
<https://urldefense.proofpoint.com/v2/url?u=https-3A__rawgit.com_w3c_aria-2D
practices_example-5Fnav_examples_alert_&d=DwMFAg&c=RoP1YumCXCgaWHvlZYR8PZh8B
v7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=ASWss0GwB
5diPwJ9Po7t5FpvV7tK4G3AltcNiUPEngU&s=tomloYjChXMUh8gCKR8iaU_Rh-ImEyc4KceZgGb
_208&e=> 

 

Please, ASAP,  provide feedback regarding your preference and on any aspect
of the visual styling in issue 536:

https://github.com/w3c/aria-practices/issues/536
<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_aria-2D
practices_issues_536&d=DwMFAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&
r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=ASWss0GwB5diPwJ9Po7t5FpvV7tK
4G3AltcNiUPEngU&s=I8zcMsmc-tRwBOcubfNWzcILDZzPuUKBUX1TIuSlkJs&e=> 

 

Many thanks,

Matt

 

-- 
Regards, James 

James Nurthen | Principal Engineer, Accessibility
Phone: +1 650 506 6781 <tel:+1%20650%20506%206781>  | Mobile: +1 415 987
1918 <tel:+1%20415%20987%201918>  | Video: james.nurthen@oracle.com
<sip:james.nurthen@oracle.com>  
Oracle Corporate Architecture
500 Oracle Parkway | Redwood City, CA 94065 
Oracle is committed to developing practices and products that help protect
the environment