[seqfan] Re: OEIS Frontend Redesign

[Alexander Craggs]

Google provides a series of guidelines for accessible website design.  They suggest:

- At least 60% of the text on a page is at least 12px in size[0]
- All tap targets are larger than 48px x 48px[1]

This is taken further by both the UK[2] and US[3] government, which both suggest a minimum font size of 16px.  We should keep in mind that whilst we might be able to read the 8 - 10px fonts used by OEIS, those with limited eyesight may not be able to.  A critical mathematical resource like the OEIS should absolutely be accessible to as many people as possible.

---

> I think there is a need for two frontends: one like the current one, which works for the submitter and editor, and one for the other users.

I really like this as a concept.  Expecting one level of abstraction of the information contained within the OEIS to work for all users is really unlikely given the huge range of skill sets that like using it.  Heck, I was 16 when I first rewrote the OEIS frontend 8 years ago:

https://github.com/popey456963/oeis-frontend

16 year old me didn't know anything about most of the sequences he was seeing.  He just enjoyed the webcam, slowly scrolling through random numbers!  That being said, multiple frontends does scale the amount of work it takes to maintain a service.  Perhaps a middle ground could be reached through the use of configuration, or hiding complex functionality behind 'advanced' tabs as suggested in a prior message in this thread.

Regards,
Alexander.

[0] https://developer.chrome.com/docs/lighthouse/seo/font-size
[1] https://developer.chrome.com/docs/lighthouse/seo/tap-targets
[2] https://designnotes.blog.gov.uk/2022/12/12/making-the-gov-uk-frontend-typography-scale-more-accessible/
[3] https://accessibility.digital.gov/visual-design/typography/

On Sun, Jan 28, 2024, at 8:45 PM, Alonso Del Arte wrote:
> Rotating the phone does help a little. At least the page becomes more
> readable, but searching for sequences is still problematic: you still have
> to find the search box, because it's tiny, though it does get zoomed in a
> little more when you try to put text in.
> 
> I tried to attach a screenshot but the mailing list server complained the
> message was too big. I can send it to anyone who wants it.
> 
> Al
> 
> On Sun, Jan 28, 2024 at 3:05 PM Edwin Clark <wedwinclark at gmail.com> wrote:
> 
> > Also there is no trouble on my android phone (Samsung Galaxy S21) if I turn
> > the phone sideways.
> >
> > On Sun, Jan 28, 2024, 1:56 PM Tom Duff <eigenvectors at gmail.com> wrote:
> >
> > > On Sun, Jan 28, 2024 at 1:13 PM Peter Luschny <peter.luschny at gmail.com>
> > > wrote:
> > >
> > > >
> > > > And then there is the host of others who don't give a damn
> > > > about such things, the 18-year-old student on his way to
> > > > university who wants to look up the Catalan numbers on his
> > > > mobile on the subway (try it with your mobile, here's the
> > > > link: https://oeis.org/A000108), and just thinks to himself,
> > > > what a weird club this OEIS is, before giving up.
> > > >
> > > > I'm sorry, but I'm not seeing the problem. I look at
> > > https://oeis.org/A000108 in Safari on my iPhone 14+ and I immediately
> > see
> > > the name, the definition, the first few numbers and the most common
> > > application immediately (counts of balanced parentheses), with no trouble
> > > at all. There's a warning that the page is pretty big, and sure enough it
> > > is. But there's nothing about the presentation on my phone that seems in
> > > the least problematic.
> > >
> > > --
> > > Seqfan Mailing list - http://list.seqfan.eu/
> > >
> >
> > --
> > Seqfan Mailing list - http://list.seqfan.eu/
> >
> 
> --
> Seqfan Mailing list - http://list.seqfan.eu/
>