Firefox

22526 readers

389 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 6 years ago

MODERATORS

k_o_t@lemmy.ml

golden_zealot@lemmy.ml

127

Mozilla is working on a big Firefox redesign, here is what it looks like (www.neowin.net)

submitted 23 hours ago by nagy@lemmy.ml to c/firefox@lemmy.ml

109 comments fedilink hide all child comments

I hope it's just a joke

you are viewing a single comment's thread
view the rest of the comments

[–] unwarlikeExtortion@lemmy.ml 2 points 10 hours ago* (last edited 3 hours ago)

But the space isn't wasted. Its used for greater legibility and generally improved accessibility and UX.

Just looking at the photo you provided, OC's words fall flat.

I know people are expected to understand the one and only design language currently in use (with its bajillion little dialects).

Even this is the same inherent lanuguage. "Home", "Back", "Forward", "Address bar", etc.

It's the same exact stuff, just displayed differently.

But the space isn't wasted. Its used for greater legibility and generally improved accessibility and UX.

But whatexactly makes the Netscape UI "inaccessible"?

The fact that it has large buttons? The fact that the buttons are realistic drawings, and not abstract lines? The fact that the buttons are labeled?

If anything, the older UI is more accessible.

Someone who doesn't know how to use either UI is bound to prefer the second one. Because it is more accessible.

There are two types of accessibility I can think of when dealing with UI: accessibility to stuff like screen readers, and accesibility to new (as in never used a computer before) users.

The Netscape UI is better in both regards: it doesn't have dropdowns (which are quite comolex to model for screen readers, and are usually full of jank). The old UI also has helpful captions for the actions. You know, the things the screen reader reads to the user. In the new Firefox, they may become "Left Arrow" if accessibility is an afterthought and generic alt text is used. Modern UI designers heading the project surely won't bother with screen readers too much anyway.

So let me ask again: Which of these is more accessible, and to whom?