[WAI Web Accessibility Laws and Policies] - Affordance for Policy clickable

[shawna-slh]

Note: This applies to current site (and redesign).

In the country-detail pages, 2 of 2 usability test participants clicked the ministry and not the policy.

I think they processed the policy only as a heading, and didn't notice that it was clickable.

We probably need to change the design so the policy itself has much stronger affordance to click, and the ministry much less. Probably move the link out of the heading -- even though it will be redundant with the heading, it will be much more apparent that that is the main thing to click on...

[yatil]

Maybe we could have a “Go to policy button” in a gutter on the right or something.

[yatil]

Hi @slhenry, I see that this is an issue in the current design as well. Do you feel we have to address it before the redesign? It impacts how to go about preparing this repository for the redesign (#314).

[yatil]

Brainstorming with @slhenry:

• Not linking the header
• Writing something like “Links to policy: English, Finnish, …”

for both versions.

[iamjolly]

I like it. I can run with that in some prototype changes.

[iamjolly]

This has been addressed in commit 4579294.

[shawna-slh]

Sorry I missed the questions to me earlier. :(
How much work would it be to implement in the current design as well? That would be good to do... but maybe not worth it?

[iamjolly]

How much work would it be to implement in the current design as well? That would be good to do... but maybe not worth it?

This might take a couple of hours to do, maybe a little more if there are any snags with back-porting the rendering component for URLs.

Would the benefits be that having it in the current design will allow us to publish the update ahead of the re-launch?

[shawna-slh]

Would the benefits be that having it in the current design will allow us to publish the update ahead of the re-launch?

Yes! As soon as it is approved, we can update it on the current site.

Ideally, we would do both -- update the current site, and have it ready for the redesigned site.

[yatil]

It deepens on what we want to port over to the old/current design: If it is just the way headings are displayed, that is easy to do. If we also want styling that fits into the old/current design, that might be a more laborious task, and we have to decide if it is worth it.

[sharronrush]

Not worth the trouble in my opinion.We have this for years, no need to struggle for a few weeks of display.

…

On Wed, Nov 15, 2017 at 9:46 AM, Eric Eggert ***@***.***> wrote: It deepens on *what* we want to port over to the old/current design: If it is just the way headings are displayed, that is easy to do. If we also want styling that fits into the old/current design, that might be a more laborious task, and we have to decide if it is worth it. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#313 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGqv06dh4pRWC4QdwNeXsw2Jv6h-YA-Bks5s2wc6gaJpZM4P3YYj> .

-- Sharron Rush | Executive Director | Knowbility.org | @knowbility *Equal access to technology for people with disabilities*

[shawna-slh]

It deepens on what we want to port over to the old/current design

The issue that we found in usability testing -- taking the links out of the headings. Don't really care about styling at this point.

[yatil]

@slhenry But the links are still in the header area, if there is an English version, it is the header. The solution consists of changing how links look (prepend language info) and making a clear separation of the header area to emphasize it. (Because people clicked the agencies before.) So I wonder if doing one thing but not the other is less effective?

[iamjolly]

I have worked on a couple of mockups based on Law/Policies with a single language (like United States) and ones with multiple languages (like Switzerland) in an attempt to address this. These have their flaws, but they might help resolve the confusion noted in usability testing.

[yatil]

Hi Robert, I think we want to keep the names of the law/policy for SEO/general find ability reasons. For example Germans might know about BITV and would easily recognize that. If we remove the name from the page, it might be disorienting. What about the following approach:

Federal Law on…

Official Law/Policies page(s):

• English
• French: French name of Law (francaise)
• German: German name of Law (deutsch)

[shawna-slh]

Thanks, Robert!

Agree with @yatil that we want the name linked. I know that will mean some redundancy when only one language, but I think necessary to address usability. I like @yatil 's idea above. (except "pages(s)" -> "pages" for simplicity ;-)

Maybe easiest to talk by phone. Ping me in IRC when available.

(Minor point: Do we want the language linked at the beginning?)

[shawna-slh]

I also wonder about having the links in the heading box or outside of it...

I'd like to share my observations from usability testing with y'all verbally (to hard to type up)

Thanks.

[yatil]

We would have laws/policy and page/pages change based on the type and the number of pages (because we now could do that). :-)

I have the language linked at the beginning so the link starts at the same position in each line, otherwise, it might be distracting with the underlines.

We specifically wanted to keep this in the header to make the connection to the heading text.

[yatil]

We just had a call and agreed on a variant of the following mockup:

With the following changes:

• Move list to policies links out of header.
• Add headings for the details and the links to the policies.
  • No colons.
• Do not (visually) link the languages at the start of the link.

[shawna-slh]

• unbold other links

[yatil]

• Backport into the old design

[yatil]

@slhenry @iamjolly Can you review and OK the changes, then I can do the backport into the old design.

https://w3c.github.io/wai-policies-prototype/policies/finland/

[iamjolly]

@yatil - These changes all look done to me.

One minor difference I see is that the country page policy title in the <header> is no longer wrapped in an <h2> so there is a skipped heading level as well as the title isn't visually bold anymore.

I'll fix that now and see how that changes things.

Update: I don't know where that is being set... @yatil, is that in the jekyll templates for multilang-policy-title?

[yatil]

@iamjolly See that is why I need your eyes. Yes, I use multilang-policy-title. Fix is coming right now :-)

[yatil]

Fixed!

[iamjolly]

Confirmed. Thank you @yatil!