search

AlaskaAirlines / auro-flight

HTML custom element that supports Alaska's flight result experience
https://auro.alaskaair.com/components/auro/flight
Apache License 2.0
3 stars 2 forks source link

auro-flight: Airport code definitions #94

Open erikalanghauser opened 1 year ago

erikalanghauser commented 1 year ago

Is your feature request related to a problem? Please describe.

In the current legacy flight results (matrix) experience, when you hover over any airport code, it defines that airport code for the guest. This was identified as a feature lacking from the microsite/auro-flight experience, as some guests in user studies hovered over the airport codes, layover airports and 'all airports' experience more frequently, to figure out where it was if they were unfamiliar with the airport.

image

Describe the solution you'd like

Legacy uses the built in browser's tooltip, but would assume we may want to use our auro-popover or some variant. Open to whatever design works best given the latest workshop and push for consistency across all usage of flight details :)

The current MOW experience has no solution to this and does not define the city pairs in the Details either. Hover will not help on the new mobile/tablet experiences, but the new mobile responsive experience leverages the latest Details modal, which defines each airport code there.

Describe alternatives you've considered

No response

Additional context

Discussed with @leeejune post- Flight Details Workshop work.

Patrick-Daly-AA commented 1 year ago

2 notes from discussing with the team: 1) We'll need to make sure that supporting this change doesn't have impacts on accessibility 2) We will need to make sure that the place we pull data from is a public API that is up to date and maintained. Additionally, for this API we'll need to make sure we're properly aligned on the names for the airports/cities (ie. SEA being "Seattle" or "Seattle/Tacoma International Airport")

blackfalcon commented 1 year ago

There is an open API call that already exists that is a legacy call to shopping/ETInfo. I reached out to AP1s of the respective teams and will see what there is out there we can use.

The one I reference, if you pass in SEA you get this return 

{
  "code": "SEA",
  "type": "APT",
  "name": "Seattle",
  "region": "WA",
  "country": "US",
  "alaskaFlysToAirport": true,
  "horizonFlysToAirport": true,
  "codeshareAirport": true,
  "lat": "47.26.37N ",
  "long": "122.18.07W",
  "itmName": "Seattle",
  "station": "Seattle/Tacoma Intl."
}