A chart you can control: keep the range and selected point in view
Design period selection, point details and return so readers retain the data context using touch, keyboard and other supported routes.
Article language: English

In this article
A finger scrolls the page when it was supposed to select Wednesday. When the user finally touches the point, the label covers its value. In a hypothetical art gallery dashboard, the chart is meant to show visits on a particular day. On a phone, it instead demands dexterity that was never part of the gallery manager's job description.
An interactive chart needs its actions designed: choosing a period, selecting a point, understanding its meaning and returning to the earlier view. Merely allowing people to enlarge the image is not enough. The reader should understand how the range changed and where to find the data needed for an answer.
Start with two tasks, not gestures
Iga, our fictional gallery manager, wants to compare two weeks and then read the visits on a selected Wednesday. The first task concerns a range, the second a particular point. Combining them in a single gesture on the chart can make the effect hard to recognise. A user should not have to guess whether they moved the period, selected a date or merely scrolled the page.
Record which questions justify the interaction. If Iga only needs a number for one day, a list of dates and values may be more convenient than a very dense line. If she is looking for a weekly pattern, a chart helps reveal relationships. Both ways of reading can be offered while keeping the same dataset and meaning.
W3C WAI's material for designers of complex graphics includes planning operation by mouse, keyboard, touch and voice, as well as access to equivalent descriptions. That is part of the user experience work. It cannot be reduced to handing a developer an image with a note saying "add accessibility".
Axes, labels and colours still need to be legible, but principles for charts in a brand's visual language (in Polish) do not by themselves explain what happens after a click. Include states before and after selection and behaviour when the range changes in the component pattern. This makes it possible to assess behaviour, not just compare two static screens.
Keep the selected period visible after a click
"Week" and "Month" buttons need a defined reference point. The current calendar week differs from the last seven days. A month may be complete or in progress. Show the actual range above the result and agree whether its boundaries are inclusive. Iga needs to know whether she is comparing complete weeks or a week with three days of observations.
If dragging can set the range, also provide a convenient route through controls. Date fields or preset periods suited to the task are possible options. Do not make a user hit a narrow handle to move the start by exactly one day. The alternative should make it possible to obtain the required range, not merely display general information about the chart.
Specify when a change is applied. With two date fields, you might wait for confirmation rather than fetch new data after every typed digit. If the update is automatic, the user should recognise its result and remain in a predictable place. Do not change the selected start while someone corrects the end without a visible reason.
A range with no results is a distinct state. A message can say that there are no observations for the selected days and let the user return to an available period. Do not silently move the dates to the nearest data. Otherwise Iga may receive a clear chart that answers a different question from the one she asked.
Data time is also part of the context. If the range includes today, the total may still be incomplete. Information about data freshness on a dashboard (in Polish) should accompany the result and its summary. A new range does not automatically mean all observations were fetched again, and a new read does not make an ongoing day complete.
When comparing two periods, keep both clearly identified. "Previously" is not enough once an image is saved or a view shared. Define the comparison: corresponding weekdays, the same dates in another month or two manually selected intervals. A designer needs that rule before choosing a transition animation.
A point needs an identity, not just a colour
The detail should identify the series, date, value and unit. "Wednesday: 18" is not enough if the chart contains both exhibition visits and workshop attendance. Recognising a point must not depend on line colour alone. The label says which measure the number belongs to, even where series cross in the same place. If both have a value of 18 on Wednesday, the detail may show both named entries. If only one is selected, the reader should be able to reach the other without hunting for a neighbouring pixel. The nearest-point selection rule needs testing on a genuinely dense section: a comfortable demonstration with three dots tells us little about a whole season.
Distinguish the point under the pointer from the point selected for further reading. The first may change as the mouse moves. The second should remain recognisable if Iga wants to move to an explanation or copy the information. If a tooltip disappears when someone tries to move onto its text, the interaction does not let them finish the task.
On a phone, a single tap can open a persistent detail below the chart or in a designated panel. The user should understand how to close it and return to the chart. If the detail opens a separate dialog, closing it should return focus, the indication of which element receives keyboard actions, to the point or control that opened it. If that point has disappeared after a range change, the design must specify another logical return location, such as the start of the chart with its current period description. A tiny popup directly under a finger is hard to read. Do not assume a double tap or long press will be obvious to everyone.
Keyboard use needs a predictable way in, movement between values and a way out. Focus should be visible and not disappear beneath a label. With many points, define navigation so that someone does not have to traverse an entire year in one long sequence of Tab presses.
Highcharts describes an accessibility module that adds keyboard navigation through points, menus and other chart controls. This is a feature of a particular library. Acceptance of your own component requires appropriate configuration and an actual test; the module's name in a project does not confirm the whole journey from selecting a period to reading Wednesday.

A screen reader needs a comprehensible introduction: what the chart shows, which period is selected and how to reach the details. A screen reader conveys content through speech, among other means. Reading a single point without its series name and unit can produce a number that cannot be used. The description should preserve the same distinctions as the visible detail.
Highcharts' advanced configuration documentation describes point and series descriptions and, for large datasets, a limit on exposing individual points to screen readers by default. Do not assume a small and a large series will be read identically. For your chart, decide which information and actions the user needs at the actual data volume.
In an Aeneia Design interaction project, these behaviours can be mapped alongside the detail content and smaller-screen view. The requirements follow from Iga's task: select the correct Wednesday and read visits for the same series by each intended route. We do not need different meanings for the data on each device.
Zooming and hiding a series change how the chart is read
After narrowing the period, decide whether the value axis keeps its scale or adjusts to the visible data. Both behaviours require a clear indication of the range. If a point in the same series now sits much higher on the chart, Iga should understand whether the number rose or the representation changed. The selected fragment should not accidentally suggest a full-year trend.
If a chart combines many observations into one point, the detail must say what that point represents. A daily average for a week is not the number of visits on a particular Wednesday. Before choosing the form, agree on aggregation, the way observations are combined. Zooming in may reveal more detailed data, but the user should recognise the change: from a weekly average to values for individual days. "More detail" alone does not explain why the number near the same part of the axis is now different.
Hiding a series through the legend is also an action. Show its visibility state and how to restore it. If every series has been hidden, do not present an empty area as a lack of data. The value exists; the user has only turned off its display. The message and available action should reflect that cause.
Alternative data, such as a table, must remain consistent with the selected range and series. If the chart shows a week and the table a whole year, explain the difference or synchronise the views. A table's presence does not automatically reproduce every interaction. People need a convenient way to answer the same question even when they do not use the line on screen.
When assessing how AI reads charts (in Polish), axes, series and missing points are among the things checked. A person controlling a chart needs that foundation too. The correct number can still be misunderstood if an old label remains after an interaction or an incomplete period is hidden.
Aeneia Design
Prepare the data and two tasks the reader needs to perform on the chart. Let us design period selection, point details and return, with equivalent touch and keyboard routes.
Discuss control and reading of an interactive chart
Returning should restore a specific state
A "Show full period" button should not remove every filter without explanation. Iga may want to expand the time range while still viewing the same exhibition. If two different actions are needed, name them separately. Resetting the range and returning to the initial configuration are different promises.
After a period change, the selected Wednesday may be outside the view. Decide whether to clear the selection with a clear message or retain it as information outside the current range. Do not move the selection to another point merely because it occupies a similar place. A point's identity should be based on the correct date and series, not its number in the visible list.
Data updates need a similar rule. If Wednesday's value changed, the detail must reflect the new state or clearly show that it is a retained version. After returning from another tab, the user should recognise the period, series and selection they were working with. Accidentally restoring only the zoom without filters can show a different dataset in a familiar frame.
For data export (in Polish), establish whether the downloaded material covers the current range or the whole source. Include visible dates and series names in an image. A screenshot will not retain hidden explanations and will not let someone move the point later. The information needed to interpret it should travel with it.
Before website accessibility acceptance (in Polish), perform a specific task through each agreed method. In the gallery project that means selecting a week, reading Wednesday and returning to the full period without losing the exhibition filter. Record where a person lost context or could not perform an action. Do not stop at whether they could open the chart.
For acceptance, prepare two periods with different values and a day on which both series cross. Iga needs to read the correct number, change the range and return to the comparison. If she can still say which day and series she is viewing after that journey, the interaction has preserved the data's meaning. Smooth movement of the line alone does not establish that.









