WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible Dashboard Experience

for

From: Elle
Date: Feb 8, 2012 12:12PM

Steve:

Language = ASP.NET MVC3 + HTML5 + jQuery + CSS3 (with progressive
enhancement and CSS Pie). As far as audience, it will be for our members
who have purchased products from our company and want to manage various
features. I don't think the audience is as important, however, given that
this discussion might benefit a lot of people (higher ED, .gov, etc.).


Cheers,
Elle



On Wed, Feb 8, 2012 at 1:55 PM, Steve Flaukner < <EMAIL REMOVED> > wrote:

> I'm trying conceptualize the final product. I agree there would be several
> challenges but there needs to be a baseline plus in what language will this
> be done? I always say NO to tables. However that's my choice. But I'm still
> trying to digest the audience of who will be accessing this?
> On Feb 8, 2012 1:42 PM, "Vincent Young" < <EMAIL REMOVED> > wrote:
>
> > This topic has got me interested. I think the BBC changed their home page
> > so there is no longer any customization.
> >
> > I'm thinking about how this would be done:
> >
> > A table would seem to give you the basic orientation, but tables for
> layout
> > are weak. role="grid" might be your answer there.
> >
> > You have to give proper notification of when an item is:
> >
> > 1. Movable
> > 2. Active
> > 3. Moved
> > 4. Set/Saved
> >
> > Things would really all need to be drawn out with proper planning
> > concerning accessibility. I would really stress that this thing can not
> be
> > developed and then accessibility added later. Sure, it might be
> possible,
> > but you'd be in a world of hurt!
> >
> >
> > On Wed, Feb 8, 2012 at 10:00 AM, Vincent Young < <EMAIL REMOVED>
> > >wrote:
> >
> > > Seeing your other posts Steve. You are surely not robot.
> > >
> > > Sent from my iPhone
> > >
> > > On Feb 8, 2012, at 9:35 AM, Elle < <EMAIL REMOVED> > wrote:
> > >
> > > > We have some very high level wireframes, but I think the concepts are
> > > > pretty standard with regards to major technical features. We will
> have
> > > > complex infographs (which we're discussing alternate formats on
> today,
> > > > leaning towards .csv for users to consume and track data as they
> like),
> > > > there will be drag and drop capabilities for a user to customize
> > his/her
> > > > dashboard, and we will have the usual accessibility challenges of
> > dynamic
> > > > content, content structure, and good old static content. The
> dashboard
> > > may
> > > > be our biggest challenge with this redesign project, but I'm excited
> to
> > > see
> > > > how we can make it both useful for our members and universally
> > > accessible.
> > > >
> > > >
> > > > Cheers,
> > > > Elle
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Feb 8, 2012 at 11:12 AM, Steve Flaukner < <EMAIL REMOVED>
> >
> > > wrote:
> > > >
> > > >> This sounds interesting. Have you started anything in layout or
> design
> > > of
> > > >> what you want? Can you share more of what you want achieve and do
> you
> > > have
> > > >> a wish list for affairs items in the long term?
> > > >> On Feb 7, 2012 8:30 AM, "Elle" < <EMAIL REMOVED> > wrote:
> > > >>
> > > >>> All:
> > > >>>
> > > >>> Our company is undergoing a major redesign, and one feature that is
> > > high
> > > >> on
> > > >>> stakeholders' list is to have a modular dashboard experience for
> > users
> > > >> that
> > > >>> they can customize (both through toggle options and drag and drop
> > > >>> capabilities). Does anyone know of an accessible dashboard
> > experience
> > > >> that
> > > >>> I could use as a guide on how to implement this? Or, alternately,
> > does
> > > >>> anyone have recommendations on the best implementation?
> > > >>>
> > > >>>
> > > >>> Much appreciated,
> > > >>> Elle
> > > >>
> > > >>
> > > >